Configuration Information [Automatically generated, do not change]:
Machine: i586
OS: linux-gnu
Compiler: gcc -I/usr/src/packages/BUILD/bash-3.2
-L/usr/src/packages/BUILD/bash-3.2/../readline-5.2
Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586'
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i586-suse-linux-gnu'
-DCONF_VENDOR='suse' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL
-DHAVE_CONFIG_H -I. -I. -I./include -I./lib -O2 -march=i586 -mtune=i686
-fmessage-length=0 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector -g -D_GNU_SOURCE
-DRECYCLES_PIDS -Wall -pipe -g -fPIE -fprofile-use
uname output: Linux fwc151 2.6.22.17-0.1-default #1 SMP 2008/02/10 20:01:04 UTC
i686 athlon i386 GNU/Linux
Machine Type: i586-suse-linux-gnu
Bash Version: 3.2
Patch Level: 25
Release Status: release
Description:
This may seem strange, but I don't mind using ed to edit my crontab.
My $EDITOR variable is set to /usr/bin/ed.
I have 'set -o vi' in my .bashrc.
When I (in most cases inadvertedly) hit <Esc> and then v, I get
my current line in an ed session. The problem is that te stty
settings are not sane.
It was very hard to get out of this session before I knew what
was wrong.
Repeat-By:
exec bash -o vi
export EDITOR=/usr/bin/bash
<Esc> + <v>
try to use ed.
Fix:
You can use ed, but there's no echo and you have to use ^J instead of
<Enter>
After !stty sane^J ed functions normal.
Also ^Z and fg %1 (when %1 is the suspended ed command) works
After return to bash you need to give one extra <Enter> before <Esc>
works
again.
I hope this helps you to further improve Bash! Now that I know how to get out of
ed without opening a new session and killing it, this is much less of a problem.
--
Kind regards, wouter...
--
De disclaimer van toepassing op e-mail van de Gemeente
Den Haag vindt u op http://www.denhaag.nl/disclaimer
