Re: help on bash-3.2

bastl73 wrote: > Is it possible that this error relays to bash-3.2.0 ? > > If I configure kdebase-3.5.6, I get this error: Does the error persist after applying the released patches for bash-3.2? Chet -- ``The lyf so short, the craft so long to lerne.'' - Chaucer Live St

Re: bash-3.2 breaks mc (echo -e '\137')

[EMAIL PROTECTED] wrote: > Configuration Information [Automatically generated, do not change]: > Machine: amd64-linux > OS: suse90 > Compiler: gcc > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='amd64-linux' > -DCONF_OSTYPE='suse90' -DCONF_MACHTYPE='x86_64-unknown-linux-gnu' > -DCONF_VEN

Re: help on bash-3.2

bastl73 wrote: > When I downloaded bash I haven't seen a patch to this version, so I did now > installed GNU bash, version 3.00.16(1)-release (i686-pc-linux-gnu). Now all > works fine. The patches are available at: ftp://ftp.cwru.edu/pub/bash/bash-3.2-patches/ ftp://ftp.gnu.org/pub/gnu/bash/

Re: readline: edit (mode:vi) means eol unreachable

Hugh Sasse wrote: >> I'm not sure I understand the question. If the termcap/terminfo entries > > The question is about the vi edit mode for a correctly configured > terminal, with no personalization. Should the cursor keys take me > out of insert mode, or leave me in insert mode (like vim), and

bash 3.2, escape sequences

Hi Chet, hi bug-bash readers, I'm not quite getting the changes in bash's handling of escape sequences. [EMAIL PROTECTED](~)> echo '\a' '\a Ouch? This is not related to escape sequence handling: [EMAIL PROTECTED](~)> echo -E '\a' '\a [EMAIL PROTECTED](~)> echo -e '\a' ' And yet, it is: [EM

Re: bash 3.2, escape sequences

Sebastian Kapfer wrote: > I'm not quite getting the changes in bash's handling of escape > sequences. I can't reproduce your results: z4.local(1)$ ./bash --version GNU bash, version 3.2.9(5)-release (i386-apple-darwin8.8.1) Copyright (C) 2005 Free Software Foundation, Inc. z4.local(1)$ ./bash z4