Re: completion inconsistencies involving symlinks

2006-09-10 Thread Kartik K. Agaram
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

Re: completion inconsistencies involving symlinks

2006-09-09 Thread Chet Ramey
[EMAIL PROTECTED] wrote: >>> I assume my original bug is still open, though? >> >> I thought I answered that. If you prefer physical paths, use `set -o >> physical' to force them. > > I'm not sure I understand. Whether I want to use logical paths or not > seems independent of whether or not the c

Re: completion inconsistencies involving symlinks

2006-09-09 Thread nu6ohq602
I assume my original bug is still open, though? I thought I answered that. If you prefer physical paths, use `set -o physical' to force them. I'm not sure I understand. Whether I want to use logical paths or not seems independent of whether or not the command I'm currently typing only resp

Re: completion inconsistencies involving symlinks

2006-09-09 Thread Chet Ramey
[EMAIL PROTECTED] wrote: > I assume my original bug is still open, though? One solution would be to > be able to specify logical vs physical pathnames in programmable > completion. I thought I answered that. If you prefer physical paths, use `set -o physical' to force them. The completion code

Re: completion inconsistencies involving symlinks

2006-09-09 Thread nu6ohq602
The shell's concept of a logical view of the file system (the default, as specified by POSIX) is maintained by `cd' and communicated to other processes via $PWD. Other processes may or may not choose to use that information. There are environments where support for $PWD is pervasive. Ah, th

Re: completion inconsistencies involving symlinks

2006-09-08 Thread Chet Ramey
Kartik K. Agaram wrote: > 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' > -DLO

Re: completion inconsistencies involving symlinks

2006-09-06 Thread Paul Jarc
"Kartik K. Agaram" <[EMAIL PROTECTED]> wrote: > I conclude that the 'logical path' is maintained only by the shell, not in > the filesystem. If I'm right, then the whole notion of logical path is a > leaky abstraction honored only by 'cd -L' (are there any others?). I would > really like to

completion inconsistencies involving symlinks

2006-09-06 Thread Kartik K. Agaram
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