From: Joerg Sonnenberger <joerg@britannica.bec.de>
To: discuss@mdocml.bsd.lv
Subject: Re: WARNING: blocks badly nested: Oc breaks Op
Date: Fri, 17 Sep 2010 12:50:11 +0200 [thread overview]
Message-ID: <20100917105010.GB7536@britannica.bec.de> (raw)
In-Reply-To: <20100916222747.GB30810@bramka.kerhand.co.uk>
On Thu, Sep 16, 2010 at 11:27:23PM +0100, Jason McIntyre wrote:
> i don;t totally understand. Oo/Oc need not happen on the same line, so i
> consider it fair game that i can stick Oc on the end of an Op line.
Your example did not put the Oc on a separate line from the Op. So yes,
there is a difference between
.Oo
.Op ...
.Oc
and
.Oo
.Op .. Oc
and as Ingo mentioned, as soon as you replace .Op with .Sq for example,
it becomes obvious.
Joerg
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-09-17 10:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-11 7:46 Jason McIntyre
2010-09-16 21:23 ` Ingo Schwarze
2010-09-16 22:27 ` Jason McIntyre
2010-09-17 10:50 ` Joerg Sonnenberger [this message]
2010-09-17 14:08 ` Jason McIntyre
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=20100917105010.GB7536@britannica.bec.de \
--to=joerg@britannica.bec.de \
--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).