From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Brian.Inglis@Shaw.ca, linux-man@vger.kernel.org,
Deri <deri@chuzzlewit.myzen.co.uk>,
Ralph Corderoy <ralph@inputplus.co.uk>
Subject: Re: No 6.05/.01 pdf book available
Date: Mon, 14 Aug 2023 00:45:41 +0200 [thread overview]
Message-ID: <c19cfc5c-3a8f-81a0-f4de-611683cb9f41@kernel.org> (raw)
In-Reply-To: <20230813215544.xtejrxxeygzxgz7e@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 1641 bytes --]
On 2023-08-13 23:55, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2023-08-13T22:47:34+0200, Alejandro Colomar wrote:
>>> Aha - Alex says .set:
> [...]
>>> https://lists.gnu.org/archive/html/groff/2023-04/msg00213.html
>>
>> We might as well make it official in suffixes(7).
>>
>> .set troff(1) typeset output
>
> I don't think this convention is very widely used. troff(1) output is
> so seldom dealt with by users that it is little wonder to me that no
> convention has arisen here.
>
> As noted earlier somewhere, I prefer ".trout" for AT&T-compatible
> troff(1) output, and ".grout" for GNU troff(1) output. Strictly, the
> latter suffix would only be necessary if the syntax extension for
> multi-line device control commands is used, and I don't know for sure
> that late-vintage DWB troff or Research Unix troff didn't support it.
> Things got very murky with AT&T troff after the company decided it to
> try using it as a cash cow.
Hmm, then let's leave it open to discussion then.
>
>> Which made me realize .roff is not documented. Branden, as the
>> maintainer of groff(1), would you mind checking that page and adding
>> all the groff(1)-related suffixes you find (or actually, that you
>> don't find)?
>
> Sure, but I've got other things on the burner right now and might need a
> reminder.
>
Sure, I'll ping you. I see you're fixing many of my bug reports.
Thanks for the TS register, and more for making it default to 2! ;)
Cheers,
Alex
> Regards,
> Branden
--
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-13 22:46 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-07 1:16 [PATCH] scripts/LinuxManBook/gropdf: use symlink instead of hard coded groff version Brian Inglis
2023-08-07 2:46 ` No 6.05/.01 pdf book available Brian Inglis
2023-08-07 8:45 ` Alejandro Colomar
2023-08-07 9:16 ` Alejandro Colomar
2023-08-07 16:21 ` Brian Inglis
2023-08-12 0:02 ` Alejandro Colomar
2023-08-12 1:48 ` G. Branden Robinson
2023-08-12 21:32 ` Alejandro Colomar
[not found] ` <21975186.EfDdHjke4D@pip>
2023-08-11 23:51 ` Alejandro Colomar
2023-08-12 3:04 ` G. Branden Robinson
2023-08-12 21:33 ` Alejandro Colomar
2023-08-12 17:02 ` Brian Inglis
2023-08-12 20:02 ` Deri
2023-08-13 20:30 ` Brian Inglis
2023-08-13 20:47 ` Alejandro Colomar
2023-08-13 21:55 ` G. Branden Robinson
2023-08-13 22:45 ` Alejandro Colomar [this message]
2023-08-13 22:18 ` Alejandro Colomar
2023-08-14 6:49 ` Brian Inglis
2023-08-14 10:46 ` Alejandro Colomar
2023-08-13 21:47 ` hyphens at ends of pages (was: No 6.05/.01 pdf book available) G. Branden Robinson
2023-08-14 5:28 ` Brian Inglis
2023-08-14 16:06 ` No 6.05/.01 pdf book available Deri
2023-08-14 17:37 ` Alejandro Colomar
2023-08-14 20:01 ` Alejandro Colomar
2023-08-14 21:22 ` Deri
2023-08-14 21:32 ` Alejandro Colomar
2023-08-14 23:26 ` Deri
2023-08-14 21:40 ` Deri
2023-08-15 0:50 ` groff features for hyperlinked man pages (was: No 6.05/.01 pdf book available) G. Branden Robinson
2023-08-15 10:34 ` G. Branden Robinson
2023-08-18 13:50 ` Alejandro Colomar
2023-08-19 4:37 ` G. Branden Robinson
2023-10-01 12:02 ` Alejandro Colomar
2023-08-18 10:29 ` No 6.05/.01 pdf book available Alejandro Colomar
2023-08-15 0:34 ` Brian Inglis
2023-08-20 16:48 ` Deri
2023-08-20 18:54 ` Alejandro Colomar
2023-08-20 19:06 ` Brian Inglis
[not found] ` <3262525.44csPzL39Z@pip>
2023-08-21 22:02 ` Alejandro Colomar
2023-08-21 23:10 ` Deri
2023-08-21 23:45 ` Brian Inglis
2023-08-28 12:17 ` Alejandro Colomar
2023-08-28 18:24 ` Brian Inglis
2023-08-28 21:11 ` Alejandro Colomar
2023-08-07 8:29 ` [PATCH] scripts/LinuxManBook/gropdf: use symlink instead of hard coded groff version Alejandro Colomar
2023-08-07 15:01 ` Brian Inglis
2023-08-11 23:57 ` Alejandro Colomar
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=c19cfc5c-3a8f-81a0-f4de-611683cb9f41@kernel.org \
--to=alx@kernel.org \
--cc=Brian.Inglis@Shaw.ca \
--cc=deri@chuzzlewit.myzen.co.uk \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=ralph@inputplus.co.uk \
/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).