linux-man.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org
Subject: [PATCH] man1/*: ffix, change '-' to '\-' for options
Date: Wed, 1 Jul 2020 22:05:53 +0000	[thread overview]
Message-ID: <20200701220553.GA24941@rhi.hi.is> (raw)

  Change '-' to '\-' for the prefix of names to indicate an option.

Signed-off-by: Bjarni Ingi Gislason <bjarniig@rhi.hi.is>
---
 man1/locale.1       | 8 ++++----
 man1/memusage.1     | 2 +-
 man1/memusagestat.1 | 4 ++--
 3 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/man1/locale.1 b/man1/locale.1
index 587795728..5506354bd 100644
--- a/man1/locale.1
+++ b/man1/locale.1
@@ -58,7 +58,7 @@ the behavior is as follows:
 .BR \-a ", " \-\-all\-locales
 Display a list of all available locales.
 The
-.B -v
+.B \-v
 option causes the
 .B LC_IDENTIFICATION
 metadata about each locale to be included in the output.
@@ -66,7 +66,7 @@ metadata about each locale to be included in the output.
 .BR \-m ", " \-\-charmaps
 Display the available charmaps (character set description files).
 To display the current character set for the locale, use
-\fBlocale -c charmap\fR.
+\fBlocale \-c charmap\fR.
 .PP
 The
 .B locale
@@ -195,8 +195,8 @@ in the shell profile file so that the custom locale will be used in the
 subsequent user sessions:
 .PP
 .EX
-$ \fBmkdir -p $HOME/.locale\fP
-$ \fBI18NPATH=./wrk/ localedef -f UTF-8 -i fi_SE $HOME/.locale/fi_SE.UTF-8\fP
+$ \fBmkdir \-p $HOME/.locale\fP
+$ \fBI18NPATH=./wrk/ localedef \-f UTF-8 \-i fi_SE $HOME/.locale/fi_SE.UTF-8\fP
 $ \fBLOCPATH=$HOME/.locale LC_ALL=fi_SE.UTF-8 date\fP
 $ \fBecho "export LOCPATH=\e$HOME/.locale" >> $HOME/.bashrc\fP
 $ \fBecho "export LANG=fi_SE.UTF-8" >> $HOME/.bashrc\fP
diff --git a/man1/memusage.1 b/man1/memusage.1
index 9292fb8f0..ce50e6f16 100644
--- a/man1/memusage.1
+++ b/man1/memusage.1
@@ -55,7 +55,7 @@ can also be intercepted.
 can output the collected data in textual form, or it can use
 .BR memusagestat (1)
 (see the
-.B -p
+.B \-p
 option,  below)
 to create a PNG file containing graphical representation
 of the collected data.
diff --git a/man1/memusagestat.1 b/man1/memusagestat.1
index 411622446..a1c40cd86 100644
--- a/man1/memusagestat.1
+++ b/man1/memusagestat.1
@@ -31,7 +31,7 @@ creates a PNG file containing a graphical representation of the
 memory profiling data in the file
 .IR datafile ;
 that file is generated via the
-.I -d
+.I \-d
 (or
 .IR --data )
 option of
@@ -41,7 +41,7 @@ The red line in the graph shows the heap usage (allocated memory)
 and the green line shows the stack usage.
 The x-scale is either the number of memory-handling function calls or
 (if the
-.I -t
+.I \-t
 option is specified)
 time.
 .SH OPTIONS
-- 
2.27.0

             reply	other threads:[~2020-07-01 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-01 22:05 Bjarni Ingi Gislason [this message]
2020-07-02 10:25 ` [PATCH] man1/*: ffix, change '-' to '\-' for options Michael Kerrisk (man-pages)

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=20200701220553.GA24941@rhi.hi.is \
    --to=bjarniig@rhi.hi.is \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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.
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).