[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

please remove or allow users to revert new symlink completion behaviour

From: gnu
Subject: please remove or allow users to revert new symlink completion behaviour
Date: Thu, 22 Nov 2001 18:53:46 -0800
User-agent: Mutt/1.3.23i

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' -DSHELL -DHAVE_CONFIG_H   -I.  -I. -I./include -I./lib -g
uname output: Linux helium 2.4.13 #3 Sat Nov 3 15:31:02 PST 2001 i686 unknown
Machine Type: i686-pc-linux-gnu

Bash Version: 2.05a
Patch Level: 0
Release Status: release


as per the CHANGES file for 2.05a:

c.  The completion code no longer appends a `/' or ` ' to a match when
    completing a symbolic link that resolves to a directory name, unless
    the match does not add anything to the word being completed.  This
    means that a tab will complete the word up to the full name, but not
    add anything, and a subsequent tab will add a slash.

i'm sure i'm not the only bash user who has been finding himself bitten over
and over again by this fundamental change to the way bash's filename
completion behaviour works.

i personally can't think of any good reason this was done - perhaps i'm
missing something?  but in any case, it's a very big change from the point
of view of someone who uses filename completion for everything (sometimes
even to the point where i'm completing the third letter of a three-letter
filename :).  i would suggest reverting this to the old behaviour by
default, and providing some sort of option (an environment variable or set
command) to turn it on if desired.

thanks for your attention to this.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]