After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 698062 - cli: exclude obsolete options from nmcli help
cli: exclude obsolete options from nmcli help
Status: RESOLVED OBSOLETE
Product: NetworkManager
Classification: Platform
Component: nmcli
git master
Other Linux
: Normal normal
: ---
Assigned To: Jiri Klimes
NetworkManager maintainer(s)
Depends on:
Blocks: tracker-nmcli
 
 
Reported: 2013-04-15 14:11 UTC by Pavel Simerda
Modified: 2020-11-12 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Pavel Simerda 2013-04-15 14:11:00 UTC
Using 'cli-enhance' branch, the following configuration objects are being offered:

OBJECT
  g[eneral]       NetworkManager's general status and operations
  n[etworking]    overall networking control
  r[adio]         NetworkManager radio switches
  c[onnection]    NetworkManager's connections
  d[evice]        devices managed by NetworkManager

My understanding is that 'general' is obsoleted by 'networking' and 'radio' and therefore shouldn't be in the quick help. There may be other obsolete options more deep in the command syntax that would deserve some care.
Comment 1 Jiri Klimes 2013-04-15 16:43:23 UTC
No, 'general' is not obsoleted, the help is up-to-date.
Basically, previous 'nm' was split into: 'general', 'networking' and 'radio'.
General currently contains these subcommands: status, logging, permissions.
(The 'status' show various NM status information including radio switches).

What should probably be removed is the old 'nm' that is still kept in the code
for backwards compatibility (but not in the help).
Comment 2 Pavel Simerda 2013-04-15 20:19:40 UTC
(In reply to comment #1)
> No, 'general' is not obsoleted, the help is up-to-date.

Ah, I see.

> Basically, previous 'nm' was split into: 'general', 'networking' and 'radio'.

Then 'nmcli general status' should be obsoleted as it is networking+radio. But then we have only 'permissions' and 'logging' and I don't think they need to be hidden behind general.

I would imagine something like:

OBJECT
  n[etworking]    overall networking control
  r[adio]         NetworkManager radio switches
  c[onnection]    NetworkManager's connections
  d[evice]        devices managed by NetworkManager
  p[ermissions]   ...
  l[ogging]       ...

As a sidenote, 'permissions' could be also viewed as access control (acl).

> General currently contains these subcommands: status, logging, permissions.
> (The 'status' show various NM status information including radio switches).
> 
> What should probably be removed is the old 'nm' that is still kept in the code
> for backwards compatibility (but not in the help).

Just ideas (I actually thought this was the consensus). Reopening to get them evaluated properly.
Comment 3 Jiri Klimes 2013-04-16 11:55:48 UTC
(In reply to comment #2)
> 
> Then 'nmcli general status' should be obsoleted as it is networking+radio. But
> then we have only 'permissions' and 'logging' and I don't think they need to be hidden behind general.

'nmcli general status' doesn't only contain radio+networking state, but several additional fields, like RUNNING, VERSION, STATE. And we may add others in future.

Also, I suppose we add additional commands under general in future.
Comment 4 Pavel Simerda 2013-04-16 13:09:54 UTC
I consider running nmcli without an instance of NetworkManager an error condition, so that wouldn't need specific status. Anyway, we can leave the discussion for later.
Comment 5 Dan Winship 2013-05-02 15:59:56 UTC
NM bugzilla reorganization... sorry for the bug spam.
Comment 6 André Klapper 2020-11-12 14:26:58 UTC
bugzilla.gnome.org is being shut down in favor of a GitLab instance. 
We are closing all old bug reports and feature requests in GNOME Bugzilla which have not seen updates for a long time.

If you still use NetworkManager and if you still see this bug / want this feature in a recent and supported version of NetworkManager, then please feel free to report it at https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/

Thank you for creating this report and we are sorry it could not be implemented (workforce and time is unfortunately limited).