From: Kristaps Dzonsons <kristaps@bsd.lv>
To: Jason McIntyre <jmc@cava.myzen.co.uk>
Cc: tech@mdocml.bsd.lv, Joel Dahl <joel@vnode.se>
Subject: Re: `Cd' and non-pairwise-breaking in SYNOPSIS.
Date: Tue, 27 Mar 2012 16:42:15 +0200 [thread overview]
Message-ID: <4F71D1C7.7060700@bsd.lv> (raw)
In-Reply-To: <20120327141931.GB8234@harkle.home.gateway>
> maybe it's best not to think of Cd as an exclusively SYNOPSIS macro. why
> go to the trouble of altering current (and groff) behaviour, just to
> match the doc? it only says that because, presumably, you wrote it.
>
> i've no idea if there's a good reason for it or not. but groff does
> explicitly document how it behaves.
>
> i see no good reason for the change. but having said that, i don;t
> overly object to it.
Hi jmc,
I don't understand -- the patch makes `Cd' behave like the other special
SYNOPSIS macros instead of having it be a special case that requires
`Pp' when followed by other macros.
I suppose the existing behaviour is cause `Cd' traditionally occured in
SYNOPSIS sections on its own. But the existence of pim(4) and friends
shows this is no longer the case.
Also, where do you see groff explicitly documenting the zany SYNOPSIS
line-breaking behaviour? I can only find notes in the doc.tmac source
itself.
Thanks,
Kristaps
--
To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2012-03-27 14:42 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-27 13:54 Kristaps Dzonsons
[not found] ` <20120327141931.GB8234@harkle.home.gateway>
2012-03-27 14:42 ` Kristaps Dzonsons [this message]
2012-04-15 21:15 ` 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=4F71D1C7.7060700@bsd.lv \
--to=kristaps@bsd.lv \
--cc=jmc@cava.myzen.co.uk \
--cc=joel@vnode.se \
--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).