[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bashbug chooses wrong $EDITOR executable

From: Villeneuve
Subject: bashbug chooses wrong $EDITOR executable
Date: Tue, 9 Jun 2009 11:01:23 -0400

Configuration Information [Automatically generated, do not change]:
Machine: i686
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i686' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i686-pc-linux-gnu' 
 -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib   
uname output: Linux hilo 2.6.9-67.0.20.ELsmp #1 SMP Wed Jun 18 12:40:47 EDT 
2008 i686 GNU/Linux
Machine Type: i686-pc-linux-gnu

Bash Version: 4.0
Patch Level: 24
Release Status: release

        I'm using my own version of emacs/emacsclient, whose bin directory
        is placed before the system's default directories in my PATH.  When
        launching bashbug, emacsclient fails to find its socket.  However,
        I have no problems using emacsclient from the shell directly.

        Create a script decorating an editor also provided by the system,
        put the script in your personal PATH, set EDITOR to point to that
        script (by name, not by full path) and call bashbug.  The editor
        called is the system's one, not your personal version.

        Do not prepend system paths in front of PATH in the bashbug script.
        Instead, these default paths could be appended to PATH if necessary.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]