From: Chad Sharp <crossroads1112@riseup.net>
To: zsh-workers@zsh.org
Subject: nmcli completions
Date: Mon, 8 Jun 2015 16:44:21 -0400 [thread overview]
Message-ID: <20150608204420.GA3699@riseup.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1748 bytes --]
I'm not a subscriber to the mailing list and please forgive me if this
is the wrong place to report this.
The completions for nmcli are very incomplete and in some instances,
incorrect.
These were my steps
$ zsh -f
$ autoload -U compinit
$ compinit -i
$ nmcli <Tab>
con -- NetworkManager connections
dev -- devices managed by NetworkManager
nm -- NetworkManager status
$ nmcli con <Tab>
down -- deactivate a connection
list -- list configured connections
status -- print status of active connections
up -- activate a connection
$ nmcli dev <Tab>
disconnect -- disconnect device and prevent it from automatically
activating
list -- get detailed information about devices
status -- print status of devices
wifi -- list available wifi access points
For simplicity's sake, I'm only going one subcommand deep because if you
try to tab complete "nmcli con mod" (which should have a large amount of
options you can change in the network configuration) you only get the
"con, dev and nm" completions again.
So to starting from the top, `nmcli nm` is not a command and should not
be part of the completion at all. nmcli con and nmcli dev are valid
commands but there are several others that should be included. nmcli's
options of course, but also the remaining objects: gen, net, rad, and
age. All the objects should also have completions as well.
`nmcli con help` does show down, list, status and up but also show, add,
modify, edit, delete, reload and load. Some of these objects have
further subobjects or options themselves.
`nmcli dev help` does have disconnect, list, status and wifi but also
status and connect. As before, wifi has several subobjects and options
[-- Attachment #2: Type: application/pgp-signature, Size: 949 bytes --]
next reply other threads:[~2015-06-08 20:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-08 20:44 Chad Sharp [this message]
2015-06-08 21:10 ` Eric Cook
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150608204420.GA3699@riseup.net \
--to=crossroads1112@riseup.net \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).