Re: edit-and-execute-command (C-xC-e) doesn't use FCEDIT env variable

[Chet Ramey]

Francis Moreau wrote:
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64'
> -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-redhat-linux-gnu'
> -DCONF_VENDOR='redhat' -DLOCALEDIR='/usr/share/locale'
> -DPACKAGE='bash' -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include
> -I./lib  -D_GNU_SOURCE  -O2 -g -pipe -Wall -Wp,-D_FORTIFY_SOURCE=2
> -fexceptions -fstack-protector --param=ssp-buffer-size=4 -m64
> -mtune=generic
> uname output: Linux mars.wyplay.int 2.6.26 #25 SMP Thu Aug 14 15:32:39
> CEST 2008 x86_64 x86_64 x86_64 GNU/Linux
> Machine Type: x86_64-redhat-linux-gnu
>
> Bash Version: 3.2
> Patch Level: 33
> Release Status: release
>
> Description:
>         When I execute edit-and-execute-command realdline command by typing 
> C-xC-e,
>         it seems that bash always launch emacs whatever the setting of
> FCEDIT env variable.
>         However man bash say the opposite.

Good catch.  The command executed is actually

fc -e "${VISUAL:-${EDITOR:-emacs}}"

It's the same command for vi and emacs editing modes, though the default
for vi editing mode is `vi' instead of `emacs'.  The documentation needs
to be updated, and has for a while, since it's been this way since at
least bash-2.05.  Seven years is a long time for this to go unnoticed.

Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer

Chet Ramey, ITS, CWRU    chet@case.edu    http://cnswww.cns.cwru.edu/~chet/