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='bash' -DSHELL -DHAVE_CONFIG_H -I. -I../bash -I../bash/include -I../bash/lib -g -O2 uname output: Linux greenwood 2.6.8-1-k7 #1 Thu Nov 25 04:13:37 UTC 2004 i686 GNU/Linux Machine Type: i486-pc-linux-gnu
Bash Version: 3.1 Patch Level: 0 Release Status: release Description: I sometimes forget to run hash -r after sticking something new in my path, and get confused. One thing I've always been hazy on is whether there is a way in unix to connect to a 'dir-contents-changed' signal or the like, but if so I would much prefer my interactive shells at least to automaticly notice new binaries as they show up in $PATH. Its especially confusing because the 'which' command, which is the first one people learn to find out which binaries they are running. Or maybe there is already such functionality? Repeat-By: I'm sure the maintainers are familiar with how this happens. Fix: Not sure the best way, but as I said above an option to do this, with a few refs to it in appropriate places in the documentation, would be most welcome, and I think it would be good if it were the default behavior. _______________________________________________ Bug-bash mailing list Bug-bash@gnu.org http://lists.gnu.org/mailman/listinfo/bug-bash
