readline inserts bogus newline for some prompt lengths

Configuration Information [Automatically generated, do not change]: Machine: i486 OS: linux-gnu Compiler: gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='

News Line AETR . pk

Penny Companies are booming right now, and so is the entertainment sector Health Care Sector has been booming since decades, this is the next big one. Don't take my word on it, Do your research and you'll see why we recommend this one Ever wonder what it would have been to get in Microsoft ,

Here-doc lines not echoed in "source" in verbose mode

Hello list, There's one situation in which I prefer zsh's behaviour over bash's... Can anyone help me to make bash behave like zsh in this case? The fix doesn't need to be a pure shell thing, there's no problem if I need to patch the C source locally, I can keep a patched bash in ~/bin/, as this

Re: typo in test cases

walter harms wrote: > hi bash-developer, > i used the bash test suite to check busybox ash and found > two possible mistakes in the latest release. [...] > > 1. func.tests:FUCNAME=7 >possible typo: FUNCNAME ? Thanks, this is indeed a typo. > > 2. getopts5.sub: hardcoded interpreter

Re: possible non-posix behaviour with sh/bash and IFS

walter harms wrote: > Bash Version: 3.0 > Patch Level: 16 > Release Status: release > > description: > > according to this paper: http://www.unix.org/whitepapers/shdiffs.html > > "If IFS is null, there is no separator, for example: > > $ IFS=" > $ set a b c > $ echo "$*" > abc > " > > Thi

Re: comint: long lines truncated

> I don't use emacs (or > xemacs), So many "maintainers" of so many packages "asked" me (and other users) so many times to try bugs users report on software they never use, including "development" versions of these packages. So it is quite justified to write the following. Please build emacsen o

typo in test cases

hi bash-developer, i used the bash test suite to check busybox ash and found two possible mistakes in the latest release. since the fix is trivial i did not add a patch. please add a comment to the source if they are intended. re, walter 1. func.tests:FUCNAME=7 possible typo: FUNCNAME ? 2.

possible non-posix behaviour with sh/bash and IFS

Configuration Information [Automatically generated, do not change]: Machine: i586 OS: linux Compiler: gcc -I/usr/src/packages/BUILD/bash-3.0 -L/usr/src/packages/BUILD/bash-3.0/../readline-5.0 Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' -DCONF_OSTYPE='linux' -DCONF_MACHTYPE='i586-

Re: completion inconsistencies involving symlinks

But bash doesn't know whether or not the command only respects physical paths. You have to tell it, and `set -o physical' is the way to do that. Ah, I finally understood what 'set -o physical' does. Here's my updated default programmable completion function for various commands now: default