tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: tech@mdocml.bsd.lv
Subject: Re: Assertions on missing argument to .SH
Date: Fri, 18 Nov 2011 18:26:47 +0100	[thread overview]
Message-ID: <20111118172647.GA27197@britannica.bec.de> (raw)
In-Reply-To: <20111117002455.GA19655@britannica.bec.de>

On Thu, Nov 17, 2011 at 01:24:55AM +0100, Joerg Sonnenberger wrote:
> Hi all,
> the logic to skip non-ASCII bytes exposed a bug in the current man
> parser. Consider the following input:
> 
> 	.SH
> 	.RS
> 
> This hits the man_node_append assertion that the parent is a block when
> allocating the body for .RS, since it ends up as node of .SH's head.
> I'm not sure what the best solution is here -- ideas?

Looking at this in more detail -- why are .SH and .SS MAN_SCOPED?
It doesn't seem to make any sense and dropping it seems to work fine.

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

      reply	other threads:[~2011-11-18 17:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-17  0:24 Joerg Sonnenberger
2011-11-18 17:26 ` Joerg Sonnenberger [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=20111118172647.GA27197@britannica.bec.de \
    --to=joerg@britannica.bec.de \
    --cc=tech@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).