Linux Manual Pages development
 help / color / mirror / Atom feed
From: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
To: Michael Kerrisk <mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH 1/2] man-pages.7: tfix
Date: Sun, 29 Jan 2017 16:21:12 +0100	[thread overview]
Message-ID: <20170129152113.9770-1-jwilk@jwilk.net> (raw)

Escape hyphens when explaining how to escape hyphens.

Signed-off-by: Jakub Wilk <jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
---
 man7/man-pages.7 | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/man7/man-pages.7 b/man7/man-pages.7
index 87c9a5dc0..1fbc37547 100644
--- a/man7/man-pages.7
+++ b/man7/man-pages.7
@@ -833,7 +833,7 @@ or when writing options that have a leading dash, such as in
 .IR "ls\ \-l"),
 use the following form in the man page source:
 
-    \\-
+    \\\-
 
 This guideline applies also to code examples.
 .SS Character constants
-- 
2.11.0

--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

             reply	other threads:[~2017-01-29 15:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-29 15:21 Jakub Wilk [this message]
     [not found] ` <20170129152113.9770-1-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2017-01-29 15:21   ` [PATCH 2/2] futex.2, open_by_handle_at.2, seccomp.2, socket.2, console_codes.4, protocols.5, aio.7, capabilities.7, libc.7, netlink.7, raw.7, standards.7, unicode.7, uri.7, vdso.7: tfix Jakub Wilk
     [not found]     ` <20170129152113.9770-2-jwilk-tXgOlIzOKNReoWH0uzbU5w@public.gmane.org>
2017-01-29 19:34       ` Michael Kerrisk (man-pages)
2017-01-29 19:33   ` [PATCH 1/2] man-pages.7: tfix 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=20170129152113.9770-1-jwilk@jwilk.net \
    --to=jwilk-txgolizoknreowh0uzbu5w@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.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. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox