From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org, Jakub Wilk <jwilk@jwilk.net>,
Ingo Schwarze <schwarze@usta.de>
Subject: Re: [RECIPE] Pull the trigger on Mister Sed? (MR macro migration)
Date: Mon, 15 Jan 2024 13:37:37 +0100 [thread overview]
Message-ID: <ZaUnEaza41FA_Uew@debian> (raw)
In-Reply-To: <20240115120520.igveghma4xb47gpl@illithid>
[-- Attachment #1: Type: text/plain, Size: 1777 bytes --]
Hi Branden,
On Mon, Jan 15, 2024 at 06:05:20AM -0600, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2024-01-15T01:10:45+0100, Alejandro Colomar wrote:
> > I was checking the book script from Deri (Deri, could you simplify the
> > script now that we use MR? So dropping support for old BR?), and
> > noticed about syscalls.2, which has man-page references inside a tbl.
> >
> > That hasn't been migrated by the script. I guess you'd want to also
> > migrate those, right, Branden?
>
> Yes. This can be done by setting the cross references inside text
> blocks "T{"/"T}", where they can call macros. I'll test this, of
> course--calling macros from within a text block can be a chancy thing.
> I don't _expect_ problems here, since `MR` does not mess with the format
> of the output line--it does not alter line length, indentation, or
> vertical spacing. I trust but will verify.
>
> I also see several references that didn't get converted ca. line 850
> because my sed script cowardly refused to rewrite lines with *roff
> comments in them. So I'll search for more stragglers like this.
>
> I will therefore be back with a "RECIPE v2". I do not promise that the
> updated sed script will be any easier to look at. :P
Maybe some preparation patch can help with this?
>
> > BTW, I've amended now the author, which I forgot.
> > <https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib>
>
> Thanks! Better if I take the heat for this 15,000+-line change. As
> Ferris Bueller said to Cameron Frye, "you don't want this much heat."
> ;-)
:-)
Cheers,
Alex
>
> Regards,
> Branden
--
<https://www.alejandro-colomar.es/>
Looking for a remote C programming job at the moment.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-01-15 12:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-14 15:42 [RECIPE] Pull the trigger on Mister Sed? (MR macro migration) G. Branden Robinson
2024-01-14 18:22 ` Alejandro Colomar
2024-01-15 0:10 ` Alejandro Colomar
2024-01-15 0:11 ` Alejandro Colomar
2024-01-15 12:05 ` G. Branden Robinson
2024-01-15 12:37 ` Alejandro Colomar [this message]
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=ZaUnEaza41FA_Uew@debian \
--to=alx@kernel.org \
--cc=g.branden.robinson@gmail.com \
--cc=jwilk@jwilk.net \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@usta.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).