Linux-man Archive on lore.kernel.org
 help / color / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: [PATCH] drop spurious t comment header
Date: Fri, 24 Jul 2020 22:15:58 +1000
Message-ID: <20200724121555.e4l2okob3x3fzk5z@localhost.localdomain> (raw)
In-Reply-To: <CAKgNAkjwwxrM_ry-b1rtrVc8YjfNE=p4iAht85P+mBs6Eq0U-w@mail.gmail.com>


[-- Attachment #1: Type: text/plain, Size: 1624 bytes --]

At 2020-07-24T12:13:33+0200, Michael Kerrisk (man-pages) wrote:
> On Fri, 24 Jul 2020 at 02:03, G. Branden Robinson
> <g.branden.robinson@gmail.com> wrote:
> > it is a hint to the man
> > program to preprocess the man page text through tbl.
> 
> Yes, that's my understanding. But I believe that these days it's no
> longer needed(?). tbl(1) just gets used as needed, regardless of the
> presence of the 't' comment, right?

[A few "strace -f -e execve"s later...]

Hmm, for the man-db man(1) in Debian bullseye (testing), at least, this
is true!  And checking its own man page, it looks like it was true as
far back as April 2001 (the horizon of its Git history).

I guess there are so many man pages that embed tables without including
the hint that the man-db maintainers decided not to leave the comment to
chance.  The only other man-like program I know if in anything like wide
use on Linux systems is mandoc, which does all its own parsing and
doesn't depend on a *roff at all.

Retaining an accurate comment would be a kindness to other man
implementations I'm not aware of and to weirdos like me who run groff
directly because we develop it (though admittedly, even for us, there is
the crutch of grog(1)).  But I'll grant--these populations may be small.

> See my comments above. For 15 years or at least, I've not paid any
> attention to adding the 't' comments when I added tables to pages, and
> I do recall anyone reporting ill effects. So, I'm inclined to apply
> Mike's patch, but will hold off a moment, in case there's other
> feedback.

Sounds fair.

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23 21:53 Mike Frysinger
2020-07-24  0:03 ` G. Branden Robinson
2020-07-24 10:13   ` Michael Kerrisk (man-pages)
2020-07-24 12:15     ` G. Branden Robinson [this message]
2020-07-24 12:30       ` Michael Kerrisk (man-pages)
2020-07-24 13:13         ` Stefan Puiu
2020-07-24 15:17           ` Michael Kerrisk (man-pages)

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=20200724121555.e4l2okob3x3fzk5z@localhost.localdomain \
    --to=g.branden.robinson@gmail.com \
    --cc=linux-man@vger.kernel.org \
    --cc=mtk.manpages@gmail.com \
    /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

Linux-man Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-man/0 linux-man/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-man linux-man/ https://lore.kernel.org/linux-man \
		linux-man@vger.kernel.org
	public-inbox-index linux-man

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-man


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git