On Wed, Jul 16, 2008 at 02:24:00AM +, David Lutterkort wrote:
> On Mon, 2008-07-14 at 11:57 +0100, Daniel P. Berrange wrote:
> > Everyone[1] seems to be doing funky bash auto-completion for commands these
> > days, so I thought I'd make a stab at doing something for virsh.
>
> I guess the comp
On Mon, Jul 14, 2008 at 11:57:07AM +0100, Daniel P. Berrange wrote:
> Everyone[1] seems to be doing funky bash auto-completion for commands these
> days, so I thought I'd make a stab at doing something for virsh.
heh, I'm a bash user, but never use completion except for filename in the
path ...
On Mon, 2008-07-14 at 11:57 +0100, Daniel P. Berrange wrote:
> Everyone[1] seems to be doing funky bash auto-completion for commands these
> days, so I thought I'd make a stab at doing something for virsh.
I guess the completions I did previously[1] never were committed then -
I'm using them quite
On Mon, Jul 14, 2008 at 11:57:07AM +0100, Daniel P. Berrange wrote:
> Everyone[1] seems to be doing funky bash auto-completion for commands these
> days, so I thought I'd make a stab at doing something for virsh.
>
> First of all I needed the command line help in an easier format to deal
> with, s
Everyone[1] seems to be doing funky bash auto-completion for commands these
days, so I thought I'd make a stab at doing something for virsh.
First of all I needed the command line help in an easier format to deal
with, so I've added
virsh _complete-command commands|arguments|options
eg,
$
