[Top][All Lists]

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

completion no longer permits file arguments to /bin/sh

From: Andy Valencia
Subject: completion no longer permits file arguments to /bin/sh
Date: Thu, 4 Apr 2013 10:56:35 -0700 (PDT)

Configuration Information [Automatically generated, do not change]:
Machine: i486
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i486' 
-DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='i486-pc-linux-gnu' 
-DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -DSHELL 
-DHAVE_CONFIG_H   -I.  -I../bash -I../bash/include -I../bash/lib  
-D_FORTIFY_SOURCE=2 -g -O2 -fstack-protector --param=ssp-buffer-size=4 -Wformat 
-Werror=format-security -Wall
uname output: Linux k9 3.2.0-4-686-pae #1 SMP Debian 3.2.39-2 i686 GNU/Linux
Machine Type: i486-pc-linux-gnu

Bash Version: 4.2
Patch Level: 37
Release Status: release

        If one has a file "data.txt" and a shell script "x", it used to
        be possible to run this with "sh x dat<tab>" and have the file argument
        completed to "data.txt".  As of Debian Wheezy update completion
        only recognizes subdirectories as possible arguments.

        Create an executable shell script "x".
        Put some text in a readable file "data.txt".
        Try to invoke script "x" as "sh x dat<tab>" and notice
        that completion does not work for data.txt.

        Interestingly, "./x dat<tab>" *does* work.  So this has to do
        with how bash looks at file arguments to explicitly invoked
        scripts passed to "sh" as the command.

reply via email to

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