I have a problem with history-search-backward & history-search-forward behaving differently on two machines. The first machine is running Redhat Gnu/Linux version 7.3 with bash version 2.05a Here is the autogenerated info from bashbug: 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' -DCON\ F_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DSHELL -DHAVE_CONFIG_H -D_GNU_SOURCE -I\ . -I. -I./include -I./lib -O2 -march=i386 -mcpu=i686 uname output: Linux plato.csl.sri.com 2.4.20-20.7smp #1 SMP Mon Aug 18 14:46:14 EDT 2003 i68\ 6 unknown Machine Type: i686-pc-linux-gnu Bash Version: 2.05a Patch Level: 0 Release Status: release The second machine is running Redhat Fedora Core 1 with bash version 2.05b. Here is the autogenerated info from bashbug: Configuration Information [Automatically generated, do not change]: Machine: i386 OS: linux-gnu Compiler: i386-redhat-linux-gcc Compilation CFLAGS: -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' -DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i386-redhat-linux-gnu' -DCONF_VENDOR='redhat' -DSHELL -DHAVE_CONFIG_H -I. -I. -I./include -I./lib -D_FILE_OFFSET_BITS=64 -O2 -g -pipe -march=i386 -mcpu=i686 uname output: Linux beast.csl.sri.com 2.4.22-1.2188.nptlsmp #1 SMP Wed Apr 21 20:12:56 EDT 2004 i686 i686 i386 GNU/Linux Machine Type: i386-redhat-linux-gnu Bash Version: 2.05b Patch Level: 0 Release Status: release On both machines my .inputrc contains : set meta-flag on set input-meta on set output-meta on set show-all-if-ambiguous on set visible-stats on Meta-p: history-search-backward Meta-n: history-search-forward On the machine running bash2.05a when I enter a partial line then press meta-p I get the bahavior I expect, it searches the history for the first matching line based on what has been type so far on the command line. bash# ca <meta-p pressed> bash# cat /tmp/foo On the second machine running bash2.05b when I enter a partial line then press meta-p bash ignores what has been typed so far, removes everything typed on the line and presents me with a colon. bash# ca <meta-p pressed> bash# : Why am I getting two different behaviors? Also the strangest thing is that if I copy the /bin/bash binary from the machine with the correct behavour onto the machine with the incorrect behavior it also does not behave correctly. What is going on? Thanks, - Mike Hogsett
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
