[ reviving an old thread :) ]
On 03/11/2018 03:11 PM, haaber wrote:
> Thank you Holger,
> I don't know what this 3D-thing, is I'll learn it. I have, in the
> meanwhile, tested the attached file, that distinguishes also running,
> paused and halted VM's. For the moment this is completely sufficient
Can this be included at Qubes Q4 or at some Qubes repo with tools for quick
installation?
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to qubes-users+unsubscr...
On Sunday, March 11, 2018 at 9:11:07 AM UTC-4, haaber wrote:
> Thank you Holger,
> I don't know what this 3D-thing, is I'll learn it. I have, in the
> meanwhile, tested the attached file, that distinguishes also running,
> paused and halted VM's. For the moment this is completely sufficient for
> m
On Sun, Mar 11, 2018 at 02:11:02PM +0100, haaber wrote:
> I don't know what this 3D-thing, is I'll learn it. I have, in the
> meanwhile, tested the attached file, that distinguishes also running,
> paused and halted VM's. For the moment this is completely sufficient for
> me. Maybe I'll add the com
Thank you Holger,
I don't know what this 3D-thing, is I'll learn it. I have, in the
meanwhile, tested the attached file, that distinguishes also running,
paused and halted VM's. For the moment this is completely sufficient for
me. Maybe I'll add the completion "root" when I complete "qvm-run -u",
s
On Fri, Mar 02, 2018 at 07:10:22PM +, Holger Levsen wrote:
> On Tue, Feb 27, 2018 at 03:23:50PM +0100, haaber wrote:
> > to have the shell behave nicer. If I have some free time, I might
> > customize this stub to suggest available options to all qvm-* and
> > qubes-* commands. I am surprised t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
On Fri, Mar 02, 2018 at 07:13:56PM -, 'awokd' via qubes-users wrote:
> On Fri, March 2, 2018 7:10 pm, Holger Levsen wrote:
> > On Tue, Feb 27, 2018 at 03:23:50PM +0100, haaber wrote:
> >
> >> to have the shell behave nicer. If I have some free ti
On Fri, March 2, 2018 7:10 pm, Holger Levsen wrote:
> On Tue, Feb 27, 2018 at 03:23:50PM +0100, haaber wrote:
>
>> to have the shell behave nicer. If I have some free time, I might
>> customize this stub to suggest available options to all qvm-* and
>> qubes-* commands. I am surprised that I might
On Tue, Feb 27, 2018 at 03:23:50PM +0100, haaber wrote:
> to have the shell behave nicer. If I have some free time, I might
> customize this stub to suggest available options to all qvm-* and
> qubes-* commands. I am surprised that I might be the first one to
> discuss this subject (?!) Bernhard
On 03/02/2018 10:22 AM, Unman wrote:
>
> Try this:
>
> _qvm()
> { local cur
> COMPREPLY=()
> cur="${COMP_WORDS[COMP_CWORD]}"
> VMS=`qvm-ls --raw-list`
> COMPREPLY=( $(compgen -W "${VMS}" -- ${cur}) )
> }
works perfectly, thank you. Should be completed (haha) by
complete -F _qvm
On Tue, Feb 27, 2018 at 11:48:41AM +0100, haaber wrote:
> > Since Q4 much admin work is done on the command line. So it makes sense
> > to learn bash to autocomplete nicely. I tried this in dom0:
> >
> > _qvm()
> > { local cur VMS
> > COMPREPLY=()
> > cur="${COMP_WORDS[COMP_CWORD]}"
> >
> Since Q4 much admin work is done on the command line. So it makes sense
> to learn bash to autocomplete nicely. I tried this in dom0:
>
> _qvm()
> { local cur VMS
> COMPREPLY=()
> cur="${COMP_WORDS[COMP_CWORD]}"
> VMS=`qvm-ls | cut -f1 -d" "| grep -v NAME`
> COMPREPLY=( $(compg
Since Q4 much admin work is done on the command line. So it makes sense
to learn bash to autocomplete nicely. I tried this in dom0:
_qvm()
{ local cur VMS
COMPREPLY=()
cur="${COMP_WORDS[COMP_CWORD]}"
VMS=`qvm-ls | cut -f1 -d" "| grep -v NAME`
COMPREPLY=( $(compgen -W "${APPVMS}"
13 matches
Mail list logo
