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

completion inconsistencies if cwd contains symlinks

[Resending for third time.] 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' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/

completion inconsistencies if cwd contains symlinks

[manually resending after bashbug seems to have failed to send.] 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' -DCONF_MACHTYPE='i686-pc-linux-gnu

completion inconsistencies involving symlinks

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' -DCONF_MACHTYPE='i686-pc-linux-gnu' -DCONF_VENDOR='pc' -DLOCALEDIR='/var/local/akkartik/akk.tmp/bas