discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Warren Block <wblock@wonkity.com>
To: discuss@mdocml.bsd.lv
Subject: Paths with replaceable components
Date: Mon, 15 Dec 2014 17:19:44 -0700 (MST)	[thread overview]
Message-ID: <alpine.BSF.2.11.1412151712470.25441@wonkity.com> (raw)

Because no good deed goes unpunished, I have another markup question. 
We have another man page for the new autofs.  One of the associated 
pages refers to this path:

.Pa /net/nfs-server-ip/share-name/

"net" is a literal there, but "nfs-server-ip" and "share-name" are not.

In DocBook, I'd mark them up as <replaceable>, to indicate to the reader 
that they are not literal.  Is there a preferred mdoc way to do that in 
a path without splitting up the path components?

--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2014-12-16  0:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16  0:19 Warren Block [this message]
2014-12-16  1:38 ` Ingo Schwarze
2014-12-16 16:41   ` Warren Block
2014-12-16 20:05     ` Ingo Schwarze

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=alpine.BSF.2.11.1412151712470.25441@wonkity.com \
    --to=wblock@wonkity.com \
    --cc=discuss@mdocml.bsd.lv \
    /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).