Sven-Göran Bergh wrote:
Just source /etc/bash_completion in either .bashrc or .profile.
what would be the contents of this file, that make expansion of the
tilde work ? /etc/bash_completion is not installed on my box.
(just to make sure we're talking about the same thing:
$ ls ~/.s<TAB> should expand to ~/.ssh/ or /home/user/.ssh, but doesn't)
while we're at it, the other autocompletion thing ash doesn't support
out-of-the-box is expansion of directories in the first position on the
actual line.
for example i want to run utils/foo.sh
$ u<TAB>
doesn't expand to utils/, whereas
$ ./u<TAB>
does.
would be nice if this could be enabled using some trick.
ash will pick it up and use it in the same way as bash.
Have never had any problem with this. Works like a charm.
Brgds
/S-G
On 10/24/2014 05:20 PM, John Spencer wrote:
Matteo Croce wrote:
Refactor read_line_input to accept a list of strings which are
added byt the autocompletion suggestions.
Let ash pass the builtin command list to read_line_input to enable
completion of builtin commands as echo, printf, history, exec, etc.
nice. could this mechanism be used to expand ~ to the contents of $HOME
for autocompletion ? lack of this expansion is currently my major
annoyance with ash and the reason i still use bash...
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
