On Nov 5, 2016 20:41, "Michael B Allen" ioplex@gmail.com wrote:
I have two files:
SUM-12_schematic.pdf VMware-Workstation-Full-10.0.1-1379776.x86_64.txt
Doing:
# ls SUM<tab>
works as expected and completes the filename but doing:
# sh -f VMw<tab>
does not work. The filename is not completed.
Clearly someone is trying to "help" me and not complete a file that sh is not normally known to be used with sh.
Can someone tell me how to disable this "helpful" behavior?
Maybe the second half of this post:
https://blog.onetechnical.com/2012/06/19/disable-bash-autocompletion-on-ubun...
On Sat, Nov 5, 2016 at 6:13 PM, Andras Simon szajmi@gmail.com wrote:
On Nov 5, 2016 20:41, "Michael B Allen" ioplex@gmail.com wrote:
Can someone tell me how to disable this "helpful" behavior?
Maybe the second half of this post:
https://blog.onetechnical.com/2012/06/19/disable-bash-autocompletion-on-ubun...
Perfect. Added complete -r to the end of ~/.bashrc does the trick.
Thanks, Mike
On Sun, Nov 6, 2016 at 12:13 AM, Andras Simon szajmi@gmail.com wrote:
On Nov 5, 2016 20:41, "Michael B Allen" ioplex@gmail.com wrote:
I have two files:
SUM-12_schematic.pdf VMware-Workstation-Full-10.0.1-1379776.x86_64.txt
Doing:
# ls SUM<tab>
works as expected and completes the filename but doing:
# sh -f VMw<tab>
does not work. The filename is not completed.
Clearly someone is trying to "help" me and not complete a file that sh is not normally known to be used with sh.
Can someone tell me how to disable this "helpful" behavior?
Maybe the second half of this post:
https://blog.onetechnical.com/2012/06/19/disable-bash-autocompletion-on-ubun...
Rather than switch off bash completion completely, you can prefix "sh -f ..." with a '" for regular tab completion to take over.