discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Jason McIntyre <jmc@kerhand.co.uk>
To: discuss@mdocml.bsd.lv
Subject: Bl+Pp still causing double spacing
Date: Sat, 4 Sep 2010 17:07:27 +0100	[thread overview]
Message-ID: <20100904160751.GD27159@bramka.kerhand.co.uk> (raw)

hi. i thought this had been fixed, but it's still happening. for
reference, see openbsd's azalia(4) page.

basically it has a list like this:

	.Pp
	.Bl -tag -width blah
	.It blah
	.Pp
	.It blah
	.Pp
	.It blah
	.El

mandoc generates double blank lines between list entries when it should
really ignore the Pp's. i'm going to zap the .Pp because it's all
useless, but regardless, mandoc should not be generating double blanks,
no?

or did we have this conversation and it should?

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

             reply	other threads:[~2010-09-04 16:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-04 16:07 Jason McIntyre [this message]
2010-09-05 18:03 ` 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=20100904160751.GD27159@bramka.kerhand.co.uk \
    --to=jmc@kerhand.co.uk \
    --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).