Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 78037 - Executable completion fails if executable is in a subdirectory
Executable completion fails if executable is in a subdirectory
Status: CLOSED DUPLICATE of bug 72512
Product: Red Hat Linux
Classification: Retired
Component: bash (Show other bugs)
i686 Linux
medium Severity low
: ---
: ---
Assigned To: Tim Waugh
Depends On:
  Show dependency treegraph
Reported: 2002-11-18 00:45 EST by William Shubert
Modified: 2008-05-01 11:38 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2002-11-18 09:05:02 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description William Shubert 2002-11-18 00:45:55 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.6 (X11; Linux i686; U;) Gecko/20020830

Description of problem:
In bash 1, if I have a subdirectory "veryLongDir" containing the executable
"longerExecutable", I can run it by typing "./ver<tab>", at which point
"./veryLongDir/" appears, then I can type "lon<tab>" and the full
"./veryLongDir/veryLongExecutable " appears, ready for me to type arguments. Great!

In Bash 2.05b, it inserts a space instead of the "/" after the "veryLongDir/",
so I type "./ver<tab>", get "./veryLongDir ", and then I must go and manually
backspace, press "/", then type again to get the next level. When I have a
binary several subdirectories deep, this is incredibly annoying. Since having a
directory name as the first part of a shell command is useless, it seems this is
strictly wrong behavior, it should always insert the "/" instead of the space.

Version-Release number of selected component (if applicable): 2.05b

How reproducible:

Steps to Reproduce:
1. mkdir veryLongDir
2. echo ls >veryLongDir/longerBinary
3. chmod +x veryLongDir/longerExecutable
4. ./ver<tab>

Actual Results:  Command prompt shows useless "./veryLongDir "

Expected Results:  It should show "./veryLongDir/"

Additional info:

Note that if you tab-complete as an argument, it does the right thing; "cat
./ver<tab>" will turn command prompt into "cat ./veryLongDir/". So it is only
wrong when you are typing the executable name.
Comment 1 Tim Waugh 2002-11-19 04:46:29 EST

*** This bug has been marked as a duplicate of 72512 ***

Note You need to log in before you can comment on or make changes to this bug.