I've noticed that this problem does no longer occur if bash 4.2.8 is
configured --with-bash-malloc. On my distribution (arch) bash is
configured --without-bash-malloc by default.
This is the configuration i use now (derived from the archlinux
pkgbuild):
./configure --prefix=/usr --with-curses --e
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-unknown-linux-gnu'
-DCONF_VENDOR='unknown' -DLOCALEDIR='/usr/share/local
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' -
DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='ba
Pablo RodrÃguez Fernández wrote:
> Why there are some keyboard shortcuts that don't appear on man
> and web page manual? I've found some shortcuts very useful (and
> widely knowed by bash users) on this blog:
> http://linuxhelp.blogspot.com/2005/08/bash-shell-shortcuts.html
> and most of them are
Chet Ramey wrote:
> Henning Bekel wrote:
>> Hello,
>> If I try to change READLINE_LINE and READLINE_POINT from a
>> function bound via bind -x, then setting READLINE_POINT is not
>> applied every second time I invoke the function. Instead, the
>> cursor
Hello,
If I try to change READLINE_LINE and READLINE_POINT from a
function bound via bind -x, then setting READLINE_POINT is not
applied every second time I invoke the function. Instead, the
cursor is placed at the end of the line.
Simple test case:
test_rl () {
READLINE_LINE="$READLINE_LI
