discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: "Anthony J. Bentley" <anthony@cathet.us>
To: discuss@mdocml.bsd.lv
Subject: Re: NetBSD PR bin/48438: mandoc(1) fails to handle nested double quote correctly.
Date: Tue, 10 Dec 2013 08:09:05 -0700	[thread overview]
Message-ID: <CAFRrxykRVi5QAyS=aaa6RXyj73+m1VAuZntXwys1GyWU0kjStA@mail.gmail.com> (raw)
In-Reply-To: <20131210092643.GA25354@danbala.tuwien.ac.at>

On Tue, Dec 10, 2013 at 2:26 AM, Thomas Klausner <wiz@netbsd.org> wrote:
> ----- Forwarded message from tsugutomo.enami@jp.sony.com -----
> % cd /usr/src
> % for c in 'nroff -mandoc' mandoc; do $c usr.bin/jot/jot.1; done | grep grep
>            grep `jot -s "" -b . 80`
>            grep `jot -s """" -b . 80`

This doesn't happen on OpenBSD's jot.1, but that's because the man
page is slightly different, not because the bug is fixed:

-.Dl "grep \`jot \-s """" \-b . 80\`"
+.Dl $ grep `jot \-s \&"\&" \-b . 80`

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

  reply	other threads:[~2013-12-10 15:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-10  9:26 Thomas Klausner
2013-12-10 15:09 ` Anthony J. Bentley [this message]
2013-12-16  0:23 ` 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='CAFRrxykRVi5QAyS=aaa6RXyj73+m1VAuZntXwys1GyWU0kjStA@mail.gmail.com' \
    --to=anthony@cathet.us \
    --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).