I hit something by accident and command line editing no longer works.
(I think I switched to the vi mode).
1. how do I get back to the emacs mode? (aka what did I hit?!)
2. how do I disable vi mode forever and ever (short of recompiling bash myself)?
thanks.
--
Sam Steingold (http://sds.podval.o
Anthony Durity wrote:
> ~ $ bash --version
> GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu)
> Copyright (C) 2007 Free Software Foundation, Inc.
>
> 2.6.28-gentoo-r5 #1 SMP Mon Apr 27 11:34:10 CEST 2009 x86_64 Intel(R)
> Xeon(R) CPU X3360 @ 2.83GHz GenuineIntel GNU/Linux
>
> === Bac
~ $ bash --version
GNU bash, version 3.2.39(1)-release (x86_64-pc-linux-gnu)
Copyright (C) 2007 Free Software Foundation, Inc.
2.6.28-gentoo-r5 #1 SMP Mon Apr 27 11:34:10 CEST 2009 x86_64 Intel(R)
Xeon(R) CPU X3360 @ 2.83GHz GenuineIntel GNU/Linux
=== Backtrace: =
/lib/libc.so.6[0x7ff
Eric Blake wrote:
> According to Chet Ramey on 6/18/2009 6:55 PM:
>> BASH PATCH REPORT
>> =
>
>> Bash-Release: 4.0
>> Patch-ID: bash40-023
>
> This appears to also be readline60-003. However, I noticed that although
> ftp://ftp.
Marc Weber wrote:
> Hi,
>
> I stumbled about another bash problem today:
>
> for item in $(false);
> echo $item
> done || { echo for failed; }
>
> doesn't fail. I think it's bad that there is no
> set -e
>
> like switch which really catches all failures of this kind.
This isn't really abo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Chet Ramey on 6/18/2009 6:55 PM:
>BASH PATCH REPORT
>=
>
> Bash-Release: 4.0
> Patch-ID: bash40-023
This appears to also be readline60-003. However, I noticed that
Esben Stien writes:
> the next thing I will try, is to build the LFS core from another
> system, cause maybe some files from my system has polluted the LFS
> core build, somehow, even though this should be impossible when
> looking at the LFS build procedure.
Well, indeed this solved the problem
