[Top][All Lists]

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

2.05b "breaks" directory completion when used from $PWD

From: michael j talarczyk
Subject: 2.05b "breaks" directory completion when used from $PWD
Date: Fri, 14 Mar 2003 14:19:04 -0800
User-agent: Mutt/1.4i

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 -O2
uname output: Linux kavala-2.rent.com 2.4.18-14 #1 Wed Sep 4 13:35:50 EDT 2002 
i686 i686 i386 GNU/Linux
Machine Type: i686-pc-linux-gnu

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


    in 2.05a, the following works correctly for my purposes, adding
    a slash and allowing me to continue to find executables in lower
    directories (assuming presence of direcetory ~/src):


    bash 2.05a responds with (the caret showing where the pointer lands):


    in bash 2.05b, the same sequence precipitates this response:


    note the pointer is moved one forward so i can't complete "down
    into", for example, ./src/bin/executable.sh .

    this is listed as a change in 2.05b's CHANGES file:

        i.  Fixed the command name completion code so a slash is no
            longer appended to a single match if there happens to be a
            directory with that name in $PWD.

    however, i don't see how the previous behaviour was broken, nor
    how to restore it to what i want. i have spent a number of hours
    investigating readline options, but to no avail.


    see above


    i went back to 2.05a but i'd like not to be restricted at this
    release level. can a readline option be specified to allow a
    directory to be completed with a slash and without moving the
    pointer forward, so i can use it to burrow down through a directory
    tree where i know executables exist?

    i am not fluent enough in bash terminology or architecture to
    suggest an option name or submit a "fix".

thanks for reading and for developing a great product!

michael j. talarczyk

reply via email to

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