On Fri, Oct 24, 2014 at 09:40:59PM +0200, John Spencer wrote: > 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) Right here (Alpine Linux, ash as default login, nothing relevant in /etc/profile), I can type as root: # ls ~id<TAB> and it is properly expanded. I can then type # ls ~idunham/.s<TAB> and it shows the several directories starting with ".s".
It works similarly as a regular user. Using Busybox 1.22.1, as compiled by Alpine. http://git.alpinelinux.org/cgit/aports/plain/main/busybox/busyboxconfig All the config options under shells->ash except "check for mail" are enabled, as is CONFIG_DESKTOP. > 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. I suspect this is a matter of searching $PATH for executables rather than searching $PWD for diretories. (For the record, I don't recall any shell that did that; I've used bash, ksh93, mksh, and pdksh, but not zsh or csh). HTH, Isaac Dunham _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
