Hi,
what about something like
function __bash_completion_loader() {
source "/etc/bash_completion.d/$1.sh" &>/dev/null
return 127
}
complete -F __bash_completion_loader ''
which will catch all programmable completions? Need change in bash.
More info at https://bugzilla.redhat.com/show_bug.cgi?i
> what about something like
>
> function __bash_completion_loader() {
> source "/etc/bash_completion.d/$1.sh" &>/dev/null
> return 127
> }
> complete -F __bash_completion_loader ''
>
> which will catch all programmable completions? Need change in bash.
> More info at https://bugzilla.redhat.c
I'm running bash 3.2.39(1)-release (under Ubuntu 8.04 (Hardy)
GNU/Linux). Neither bash.info or bash(1) documents parameter
expansion of the form:
${parameter+word}
This is different to ${parameter:+word}, is clearly implemented by
bash and is documented in the standard (The Open Group Base
Spe
"Martin Schwenke" wrote:
> Neither bash.info or bash(1) documents parameter expansion of the
> form:
>
> ${parameter+word}
It's documented, but it's easy to miss. Just before the list of
parameter expansion forms is this paragraph:
In each of the cases below, word is subject to tilde e
Martin Schwenke wrote:
> I'm running bash 3.2.39(1)-release (under Ubuntu 8.04 (Hardy)
> GNU/Linux). Neither bash.info or bash(1) documents parameter
> expansion of the form:
>
> ${parameter+word}
>
> This is different to ${parameter:+word}, is clearly implemented by
> bash and is documented i
Hi, why doesn't the second command work? (Trying to move all files into
a newly created directory.)
$ mkdir dhclient
$ mv !(dhclient) !$
bash: !: event not found
--
Yang Zhang
http://www.mit.edu/~y_z/
