Re: Install Bashdb and Bash not as root

lehe wrote: > Since the old shell is the login shell reading ./bash_profile and the new > one isn't but reading ./bashrc, how could there possibly be infinite loop > at login-in? There shouldn't be, so you should be okay there. But people rarely leave things alone. If you mutated that into a fe

Re: Install Bashdb and Bash not as root

Thanks Bob! Since the old shell is the login shell reading ./bash_profile and the new one isn't but reading ./bashrc, how could there possibly be infinite loop at login-in? You mean, new shell keeps calling itself by reading ./bash_profile? If the infinite loop happens, what would you do in those

"wait" command should wait until process TERMINATES

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='ba

Re: Install Bashdb and Bash not as root

lehe wrote: > I just solve my problem by adding the path of my newly-installed bash to the > beginning of PATH. However I now have some new questions: > > 1. The change to PATH is effective only in the current shell session. I was > wondering if it is possible to run the new bash instead of the o

Re: Install Bashdb and Bash not as root

I just solve my problem by adding the path of my newly-installed bash to the beginning of PATH. However I now have some new questions: 1. The change to PATH is effective only in the current shell session. I was wondering if it is possible to run the new bash instead of the old one everytime it i

Re: Bash keeps reloading default bind key settings

Jimi wrote: > Hi all, > > Strange condition that i can't find the solution to. > > My bash for RH 3.4.6, is 3.00.15(1) > > > I have a .inputrc file with some settings like > "\C-w": kill-region > "\M-u": upcase-word > > > The \C-w bind is different than the default ( which is to unix-word- >

Re: Missed save_parser_state() function call in pcomplete.c

> Machine Type: i586-suse-linux-gnu > > Bash Version: 4.0 > Patch Level: 0 > Release Status: release > > Description: > It seems that my last patch for pcomplete.c is not fully applied. > The line > save_parser_state (pps); > is missed and leads to a memory corruption

Re: unexpected EOF while looking for matching `)'

wer...@suse.de wrote: > Configuration Information [Automatically generated, do not change]: > Machine: i586 > OS: linux-gnu > Compiler: gcc -I/usr/src/packages/BUILD/bash-4.0 > -L/usr/src/packages/BUILD/bash-4.0/../readline-6.0 > Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i586' > -DCO

Re: Missed save_parser_state() function call in pcomplete.c

wer...@suse.de wrote: > Bash Version: 4.0 > Patch Level: 0 > Release Status: release > > Description: > It seems that my last patch for pcomplete.c is not fully applied. > The line > save_parser_state (pps); > is missed and leads to a memory corruption at the point whe

unexpected EOF while looking for matching `)'

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

Missed save_parser_state() function call in pcomplete.c

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