Problems in nmcli.1
This is automatically generated email about markup problems in a man
page for which you appear to be responsible. If you are not the right
person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated. Feel free to email me with any
questions. Note: These patches do not change the modification date of
any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.
--
Eric S. Raymond
Problems with nmcli.1:
Broken command synopsis syntax. This may mean you're using a
construction in the command synopsis other than the standard
[ ] | { }, or it may mean you have running text in the command synopsis
section (the latter is not technically an error, but most cases of it
are impossible to translate into DocBook markup), or it may mean the
command syntax fails to match the description.
List syntax error. This means .IP, .TP or .RS/.RE markup is garbled.
Common causes include .TP just before a section header, .TP entries
with tags but no bodies, and mandoc lists with no trailing .El.
These confuse doclifter, and may also mess up stricter man-page
browsers like Xman and Rosetta.
Presentation-level use of .SS could not be structurally
translated. I changed lower-level instances to .TP or .B.
--- nmcli.1-unpatched 2016-03-02 01:49:37.245643661 -0500
+++ nmcli.1 2016-03-02 01:49:47.477617367 -0500
@@ -26,40 +26,29 @@
.SH NAME
nmcli \- command\(hyline tool for controlling NetworkManager
.SH SYNOPSIS
-.ad l
.B nmcli
-.RI " [ " OPTIONS " ] " OBJECT " { " COMMAND " | "
-.BR help " } "
-.sp
-
-.IR OBJECT " := { "
-.BR general " | " networking " | " radio " | " connection " | " device " | "
agent
-.RI " }"
-.sp
-
-.IR OPTIONS " := { "
-.br
-\fB\-t\fR[\fIerse\fR]
-.br
-\fB\-p\fR[\fIretty\fR]
-.br
-\fB\-m\fR[\fImode\fR] tabular | multiline
-.br
-\fB\-f\fR[\fIields\fR] | all | common
-.br
-\fB\-e\fR[\fIscape\fR] yes | no
-.br
-\fB\-n\fR[\fIocheck\fR]
.br
-\fB\-a\fR[\fIsk\fR]
+[
+\fB\-terse\fR |
+\fB\-pretty\fR |
+\fB\-mmode\fR { tabular | multiline } |
+.br
+\fB\-fields\fR { | all | common } |
+\fB\-escape\fR { yes | no } |
+.br
+\fB\-nocheck\fR |
+\fB\-ask\fR |
+\fB\-wait\fR |
+\fB\-version\fR |
+\fB\-help\fR
+]
.br
-\fB\-w\fR[\fIait\fR]
-.br
-\fB\-v\fR[\fIersion\fR]
-.br
-\fB\-h\fR[\fIelp\fR]
+{
+.BR general " | " networking " | " radio " | " connection " | " device " | "
agent
+}
.br
-.RI "}"
+.RI "{ " COMMAND " | "
+.BR help " } "
.SH DESCRIPTION
.B nmcli
@@ -153,7 +142,7 @@
Use this object to show NetworkManager status and permissions. You can also get
and change system hostname, as well as NetworkManager logging level and
domains.
.TP
-.SS \fICOMMAND\fP := { status | hostname | permissions | logging }
+.B \fICOMMAND\fP := { status | hostname | permissions | logging }
.sp
.RS
.TP
@@ -194,7 +183,7 @@
networking. Disabling networking removes the configuration from all devices and
changes them to the 'unmanaged' state.
.TP
-.SS \fICOMMAND\fP := { [ on | off | connectivity ] }
+.B \fICOMMAND\fP := { [ on | off | connectivity ] }
.sp
.RS
.TP
@@ -232,7 +221,7 @@
Use this object to show radio switches status, or enable and disable
the switches.
.TP
-.SS \fICOMMAND\fP := { all | wifi | wwan | wimax }
+.B \fICOMMAND\fP := { all | wifi | wwan | wimax }
.sp
.RS
.TP
@@ -278,7 +267,7 @@
connected to the DHCP-enabled network the user would run "nmcli con up default"
, and when connected to the static network the user would run "nmcli con up
testing".
.TP
-.SS \fICOMMAND\fP := { show | up | down | add | edit | modify | delete |
reload | load }
+.B \fICOMMAND\fP := { show | up | down | add | edit | modify | delete | reload
| load }
.sp
.RS
.TP
@@ -330,8 +319,7 @@
.RE
.TP
.B up [ id | uuid | path ] [ifname ] [ap ] [nsp ]
[passwd ]
-.RE
-.RS
+.TP
.B up ifname [ap ] [nsp ] [passwd ]
.RS
.br
@@ -627,8 +615,7 @@
.RE
.TP
.B edit [id | uuid | path ] - edit an existing connection
-.RE
-.RS
+.TP
.B edit [type ] [con-name ] - add a
new connection
.RS
Edit an existing connection or add a new one, using an interactive editor.
@@ -649,12 +636,12 @@
\(en type of the new connection; valid types are the same as for \fIconnection
add\fP command
.IP \fIcon-name\fP 13
\(en name for the new connection. It can be changed later in the editor.
-.RE
.RS
.sp
See also \fInm-settings\fP(5) for all NetworkManager settings and property
names, and their
descriptions; and \fInmcli-examples\fP(5) for sample editor sessi
Problems in nmcli.1
This is automatically generated email about markup problems in a man
page for which you appear to be responsible. If you are not the right
person or list, please tell me so I can correct my database.
See http://catb.org/~esr/doclifter/bugs.html for details on how and
why these patches were generated. Feel free to email me with any
questions. Note: These patches do not change the modification date of
any manual page. You may wish to do that by hand.
I apologize if this message seems spammy or impersonal. The volume of
markup bugs I am tracking is over five hundred - there is no real
alternative to generating bugmail from a database and template.
--
Eric S. Raymond
Problems with nmcli.1:
Broken command synopsis syntax. This may mean you're using a
construction in the command synopsis other than the standard
[ ] | { }, or it may mean you have running text in the command synopsis
section (the latter is not technically an error, but most cases of it
are impossible to translate into DocBook markup), or it may mean the
command syntax fails to match the description.
List syntax error. This means .IP, .TP or .RS/.RE markup is garbled.
Common causes include .TP just before a section header, .TP entries
with tags but no bodies, and mandoc lists with no trailing .El.
These confuse doclifter, and may also mess up stricter man-page
browsers like Xman and Rosetta.
Presentation-level use of SS could not be structurally
translated. I changed lower-level instances to .TP or .B.
--- nmcli.1-unpatched 2016-03-02 01:49:37.245643661 -0500
+++ nmcli.1 2016-03-02 01:49:47.477617367 -0500
@@ -26,40 +26,29 @@
.SH NAME
nmcli \- command\(hyline tool for controlling NetworkManager
.SH SYNOPSIS
-.ad l
.B nmcli
-.RI " [ " OPTIONS " ] " OBJECT " { " COMMAND " | "
-.BR help " } "
-.sp
-
-.IR OBJECT " := { "
-.BR general " | " networking " | " radio " | " connection " | " device " | "
agent
-.RI " }"
-.sp
-
-.IR OPTIONS " := { "
-.br
-\fB\-t\fR[\fIerse\fR]
-.br
-\fB\-p\fR[\fIretty\fR]
-.br
-\fB\-m\fR[\fImode\fR] tabular | multiline
-.br
-\fB\-f\fR[\fIields\fR] | all | common
-.br
-\fB\-e\fR[\fIscape\fR] yes | no
-.br
-\fB\-n\fR[\fIocheck\fR]
.br
-\fB\-a\fR[\fIsk\fR]
+[
+\fB\-terse\fR |
+\fB\-pretty\fR |
+\fB\-mmode\fR { tabular | multiline } |
+.br
+\fB\-fields\fR { | all | common } |
+\fB\-escape\fR { yes | no } |
+.br
+\fB\-nocheck\fR |
+\fB\-ask\fR |
+\fB\-wait\fR |
+\fB\-version\fR |
+\fB\-help\fR
+]
.br
-\fB\-w\fR[\fIait\fR]
-.br
-\fB\-v\fR[\fIersion\fR]
-.br
-\fB\-h\fR[\fIelp\fR]
+{
+.BR general " | " networking " | " radio " | " connection " | " device " | "
agent
+}
.br
-.RI "}"
+.RI "{ " COMMAND " | "
+.BR help " } "
.SH DESCRIPTION
.B nmcli
@@ -153,7 +142,7 @@
Use this object to show NetworkManager status and permissions. You can also get
and change system hostname, as well as NetworkManager logging level and
domains.
.TP
-.SS \fICOMMAND\fP := { status | hostname | permissions | logging }
+.B \fICOMMAND\fP := { status | hostname | permissions | logging }
.sp
.RS
.TP
@@ -194,7 +183,7 @@
networking. Disabling networking removes the configuration from all devices and
changes them to the 'unmanaged' state.
.TP
-.SS \fICOMMAND\fP := { [ on | off | connectivity ] }
+.B \fICOMMAND\fP := { [ on | off | connectivity ] }
.sp
.RS
.TP
@@ -232,7 +221,7 @@
Use this object to show radio switches status, or enable and disable
the switches.
.TP
-.SS \fICOMMAND\fP := { all | wifi | wwan | wimax }
+.B \fICOMMAND\fP := { all | wifi | wwan | wimax }
.sp
.RS
.TP
@@ -278,7 +267,7 @@
connected to the DHCP-enabled network the user would run "nmcli con up default"
, and when connected to the static network the user would run "nmcli con up
testing".
.TP
-.SS \fICOMMAND\fP := { show | up | down | add | edit | modify | delete |
reload | load }
+.B \fICOMMAND\fP := { show | up | down | add | edit | modify | delete | reload
| load }
.sp
.RS
.TP
@@ -330,8 +319,7 @@
.RE
.TP
.B up [ id | uuid | path ] [ifname ] [ap ] [nsp ]
[passwd ]
-.RE
-.RS
+.TP
.B up ifname [ap ] [nsp ] [passwd ]
.RS
.br
@@ -627,8 +615,7 @@
.RE
.TP
.B edit [id | uuid | path ] - edit an existing connection
-.RE
-.RS
+.TP
.B edit [type ] [con-name ] - add a
new connection
.RS
Edit an existing connection or add a new one, using an interactive editor.
@@ -649,12 +636,12 @@
\(en type of the new connection; valid types are the same as for \fIconnection
add\fP command
.IP \fIcon-name\fP 13
\(en name for the new connection. It can be changed later in the editor.
-.RE
.RS
.sp
See also \fInm-settings\fP(5) for all NetworkManager settings and property
names, and their
descriptions; and \fInmcli-examples\fP(5) for sample editor sessi
Problems in nmcli.1
This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand. I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template. -- Eric S. Raymond Problems with nmcli.1: Ambiguous or invalid backslash. This doesn't cause groff a problem. but it confuses doclifter and may confuse older troff implementations. --- nmcli.1-unpatched 2014-06-01 20:55:07.564193226 -0400 +++ nmcli.1 2014-06-01 20:55:16.852405793 -0400 @@ -531,5 +531,5 @@ .BR nm\-online (1), .BR NetworkManager (8), .BR nm\-settings (5), -.BR nm\applet (1), +.BR nm\-applet (1), .BR nm\-connection\-editor (1). ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
Problems in nmcli.1, nm-connection-editor.1
This is automatically generated email about markup problems in a man page for which you appear to be responsible. If you are not the right person or list, please tell me so I can correct my database. See http://catb.org/~esr/doclifter/bugs.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the modification date of any manual page. You may wish to do that by hand. I apologize if this message seems spammy or impersonal. The volume of markup bugs I am tracking is over five hundred - there is no real alternative to generating bugmail from a database and template. -- Eric S. Raymond Problems with nmcli.1: Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. Or your page may add running text such as a version or authorship banner. These problems make it impossible to lift the page to DocBook. They can also confuse third-party manpage browsers and some implementations of man -k. Unknown or invalid macro. That is, one that does not fit in the macro set that the man page seems to be using. This is a serious error; it often means part of your text is being lost or rendered incorrectly. --- nmcli.1-unpatched 2013-05-24 17:08:58.597822819 -0400 +++ nmcli.1 2013-05-24 17:09:18.841822440 -0400 @@ -24,7 +24,7 @@ .TH NMCLI "1" "17 January 2013" .SH NAME -nmcli \(en command\(hyline tool for controlling NetworkManager +nmcli \- command\(hyline tool for controlling NetworkManager .SH SYNOPSIS .ad l .B nmcli @@ -531,5 +531,5 @@ .BR nm\-online (1), .BR NetworkManager (8), .BR nm\-settings (5), -.BR nm\applet (1), +.BR nm\-applet (1), .BR nm\-connection\-editor (1). Problems with nm-connection-editor.1: Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. Or your page may add running text such as a version or authorship banner. These problems make it impossible to lift the page to DocBook. They can also confuse third-party manpage browsers and some implementations of man -k. Unknown or invalid macro. That is, one that does not fit in the macro set that the man page seems to be using. This is a serious error; it often means part of your text is being lost or rendered incorrectly. --- nm-connection-editor.1-unpatched2013-05-24 05:00:53.058639796 -0400 +++ nm-connection-editor.1 2013-05-24 05:01:06.930639536 -0400 @@ -24,7 +24,7 @@ .TH NM-CONNECTION-EDITOR "1" "15 February 2013" .SH NAME -nm\-connection\-editor \(en network connection editor for NetworkManager +nm\-connection\-editor \- network connection editor for NetworkManager .SH SYNOPSIS .B nm\-connection\-editor .RI " [ " OPTIONS " ] ___ networkmanager-list mailing list networkmanager-list@gnome.org https://mail.gnome.org/mailman/listinfo/networkmanager-list
problems in NetworkManager.1, NetworkManagerDispatcher.1, nm-tool.1
This is automatically generated email about problems in a man page for which you appear to be responsible. If you are not the right person or list, tell me and I will attempt to correct my database. See http://catb.org/~esr/doclifter/problems.html for details on how and why these patches were generated. Feel free to email me with any questions. Note: These patches do not change the mod date of any manual page. You may wish to do that by hand. Problems with NetworkManager.1: 1. Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. These problems make it impossible to lift the page to DocBook. They can also confuse some implementations of man -k. --- NetworkManager.1-orig 2006-12-18 09:54:32.0 -0500 +++ NetworkManager.12006-12-18 09:55:06.0 -0500 @@ -3,6 +3,7 @@ .\" Copyright (C) 2005 Robert Love .\" .TH NETWORKMANAGER "1" +.SH NAME NetworkManager \- network management daemon .SH SYNOPSIS .B NetworkManager [\-\-no-daemon] [\-\-enable-test-devices] - Problems with NetworkManagerDispatcher.1: 1. Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. These problems make it impossible to lift the page to DocBook. They can also confuse some implementations of man -k. --- NetworkManagerDispatcher.1-orig 2006-12-18 09:55:33.0 -0500 +++ NetworkManagerDispatcher.1 2006-12-18 09:55:42.0 -0500 @@ -3,6 +3,7 @@ .\" Copyright (C) 2005 Robert Love .\" .TH NETWORKMANAGERDISPATCHER "1" +.SH NAME NetworkManagerDispatcher \- daemon that runs commands in response to off/online .SH SYNOPSIS .B NetworkManagerDispatcher [\-\-no-daemon] - Problems with nm-tool.1: 1. Missing or garbled name section. The most common form of garbling is a missing - or extra -. Or your manual page may have been generated by a tool that doesn't emit a NAME section as it should. These problems make it impossible to lift the page to DocBook. They can also confuse some implementations of man -k. --- nm-tool.1-orig 2006-12-18 09:56:26.0 -0500 +++ nm-tool.1 2006-12-18 09:56:35.0 -0500 @@ -3,6 +3,7 @@ .\" Copyright (C) 2005 Robert Love .\" .TH NM-TOOL "1" +.SH NAME nm-tool \- utility to report NetworkManager state .SH SYNOPSIS .B nm-tool - -- Eric S. Raymond ___ NetworkManager-list mailing list NetworkManager-list@gnome.org http://mail.gnome.org/mailman/listinfo/networkmanager-list
