From: Kristaps Dzonsons <kristaps@bsd.lv>
To: discuss@mdocml.bsd.lv
Subject: Re: mdocml: .Bl -column phrases ignore spacing rules for trailing
Date: Sat, 21 Aug 2010 19:29:44 +0200 [thread overview]
Message-ID: <4C700D08.3040304@bsd.lv> (raw)
In-Reply-To: <20100821160651.GA31898@iris.usta.de>
Ingo,
> Now, as you said, this does not affect column lists only,
> but literal tabs outside column lists as well.
> But in literal context, there is no issue because spacing
> is kept verbatim in any case, and outside literal context,
> tabs are discouraged anyway. So, basically, the tab vs space-tab
> surprise only affects column lists in practice.
Damn, I didn't know that it also worked as such outside of the `It'
context. Even more gross.
Note well. `It -column' can be changed to be like groff with fairly
minimal effort. In short, the MDOC_EOS flag would need to be unset if
the tab is immediately preceded by non-whitespace. It'd be only a few
lines, but I don't think this behaviour is worth following. As you
noted, the "principle of most surprise" should not hold.
That reminds me: can you put a note in mdoc.7 COMPATIBILITY?
> Given that the traditional behaviour of column lists has been
> so quirky in so many ways, i regard it as sane to make it a bit
> easier to understand at the expense of minor issues with backward
> compatibility. This is a case where i feel that idea applies.
>
> So, i propose the following patch instead.
> It works with all formatters.
I agree, for what it's worth.
Thanks!
Kristaps
--
To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv
next prev parent reply other threads:[~2010-08-21 17:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201008202251.o7KMpT4F020687@krisdoz.my.domain>
2010-08-21 11:18 ` Kristaps Dzonsons
2010-08-21 16:06 ` Ingo Schwarze
2010-08-21 17:29 ` Kristaps Dzonsons [this message]
2010-08-21 20:12 ` mdoc(7) COMPATIBILITY Ingo Schwarze
2010-08-21 20:20 ` Kristaps Dzonsons
2010-08-22 9:27 ` Kristaps Dzonsons
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=4C700D08.3040304@bsd.lv \
--to=kristaps@bsd.lv \
--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).