Bug#306043: bash executable completion doesn't work if there is a space in the executable path

[Chet Ramey]

On 4/5/24 5:21 PM, Gioele Barabucci wrote:

Control: found -1 5.2.21-2
Control: tags -1 upstream
X-Debbugs-CC: bug-b...@gnu.org

On Sat, 23 Apr 2005 15:20:19 -0700 Frederik Eaton <frede...@ofb.net> wrote:

Bash executable completion doesn't work if there is a space in the
executable path.

This issue is still partially present in current version of Bash.

The most basic case has been fixed:

     $ touch "cmd with spaces"
     $ chmod +x "cmd with spaces"
     $ PATH=$PWD:$PATH
     $ cmd<TAB>
     $ cmd\ with\ spaces

However there seems to be a linger issue that appears when multiple commands with spaces match a given prefix:

Thanks for the report. This will be fixed in the next push to the bash
devel branch.

Chet

--
``The lyf so short, the craft so long to lerne.'' - Chaucer
                 ``Ars longa, vita brevis'' - Hippocrates
Chet Ramey, UTech, CWRU    c...@case.edu    http://tiswww.cwru.edu/~chet/

OpenPGP_signature.asc
Description: OpenPGP digital signature