Re: a bug in restricted bash mode?

2007-05-14 Thread Chet Ramey
Dawid Gołuński wrote: > I think, the problem is connected with a bad argv[0] comparison. It is, > when rbash is called directly from bash level, the argv[0] equals > "rbash", and when rbash is called at login, argv[0] is > equal to "-rbash". So i thought maybe there was something like this: > > i

Re: backwards menu-complete with shift+tab

2007-05-14 Thread Chet Ramey
[EMAIL PROTECTED] wrote: > 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' -

a bug in restricted bash mode?

2007-05-14 Thread Dawid Gołuński
Hello bug-bash, I've just come across a strange problem. It's connected with restricted mode of bash program. When I invoke bash like this: /bin/bash -r it runs correctly into restricted mode: [EMAIL PROTECTED]:/$ /bin/bash -r bash: SHELL: readonly variable bash: PATH: readonly variable

Re: Path in patch

2007-05-14 Thread Chet Ramey
> Thank you for wonderful software to which I'm indebted every day. Thanks for your kind words. > I have one question. > > Why be not consistent path of patch ? > ex) "../bash-3.2-patched/", "../bash-3.2.9/", "../bash-3.2.11/" Because it doesn't matter -- `patch' doesn't care. Chet -- ``The

Re: backwards menu-complete with shift+tab

2007-05-14 Thread Paul Jarc
<[EMAIL PROTECTED]> wrote: > Specifying the key combo shift+tab is not documented. Your terminal program probably doesn't distinguish tab from shift+tab. To check, try running od, and type tab, enter, shift+tab, enter, and see if od prints the same codes for both. paul ___

backwards menu-complete with shift+tab

2007-05-14 Thread gph9mail-bashbug
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=

Path in patch

2007-05-14 Thread takuomi
Thank you for wonderful software to which I'm indebted every day. I have one question. Why be not consistent path of patch ? ex) "../bash-3.2-patched/", "../bash-3.2.9/", "../bash-3.2.11/" If it's necessary, I write patch that corrects path of patch. Sorry, my poor English... -- Takuomi Kag