netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Sowden <jeremy@azazel.net>
To: Jan Engelhardt <jengelh@inai.de>
Cc: Netfilter Devel <netfilter-devel@vger.kernel.org>
Subject: Re: [PATCH xtables-addons] doc: fix quoted string in libxt_DNETMAP man-page.
Date: Tue, 21 Jul 2020 13:48:01 +0100	[thread overview]
Message-ID: <20200721124801.GA885340@dreamlands> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2007211114060.23166@n3.vanv.qr>

[-- Attachment #1: Type: text/plain, Size: 1100 bytes --]

On 2020-07-21, at 11:16:00 +0200, Jan Engelhardt wrote:
> On Tuesday 2020-07-21 10:31, Jeremy Sowden wrote:
> > In roff, lines beginning with a single quote are control lines.  In
> > the libxt_DNETMAP man-page there is a single-quoted string at the
> > beginning of a line, which troff tries and fails to interpret as a
> > macro:
>
> Is there some escaping magic available that would make this work as
> well? I would fear that if the next person (me included) comes around
> to use an editor's "wrap at 80 cols" feature, that the quote might
> re-shift to the start of line. If all else, I'd just pick " over ' -
> in the hope that that does not have a special meaning.

Good point.  I had another look at the documentation and found escape-
sequences for opening and closing single quotes.  I'll send out a new
version of the patch.

> > -boot time). Please note that the \fBttl\fR and \fBlasthit\fR entries contain an
> > -'\fBS\fR' in case of a static binding.
> > +boot time). Please note that the \fBttl\fR and \fBlasthit\fR entries contain
> > +an '\fBS\fR' in case of a static binding.

J.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 659 bytes --]

      reply	other threads:[~2020-07-21 12:48 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-21  8:31 [PATCH xtables-addons] doc: fix quoted string in libxt_DNETMAP man-page Jeremy Sowden
2020-07-21  9:16 ` Jan Engelhardt
2020-07-21 12:48   ` Jeremy Sowden [this message]

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=20200721124801.GA885340@dreamlands \
    --to=jeremy@azazel.net \
    --cc=jengelh@inai.de \
    --cc=netfilter-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).