All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 14 Jan 2024 19:22:47 +0100	[thread overview]
Message-ID: <ZaQmd0aP1XlFiAKA@debian> (raw)
In-Reply-To: <20240114154225.5tyuiqrgwyltqmj3@illithid>

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

Hi MR. sed,

On Sun, Jan 14, 2024 at 09:42:25AM -0600, G. Branden Robinson wrote:
> Hi Alex,
> 
> All past efforts at submitting a patch for this have met with vger's
> wrath and rage--even a diffstat is too much for it tolerate.  For those
> who don't remember what this proposal is meant to achieve, here's a
> backgrounder from October[0].
> 
> groff 1.23.0 has been out for over six months[1] and every major
> GNU/Linux distribution, plus several non-major ones, is shipping it.[2]
> 
> I'm attaching two scripts, "MR-migrate.sh" and "MR.sed".  Drop them in
> the directory of your man-pages checkout, and run the first with a POSIX
> shell.
> 
> The migration script doesn't just alter the pages; it also generates
> "before.txt" and "after.txt" files containing the man page contents
> rendered as (UTF-8) plain text to verify that no changes to page content
> (apart from font style change to man page cross references attendant to
> the use of a new macro, which is user-configurable[3]) occur.
> 
> I get the following output:
> $ sh ./MR-migrate.sh
> man4/console_codes.4:324: warning: table wider than line length minus indentation
> man5/proc_pid_smaps.5:88: warning: table wider than line length minus indentation
> troff:man7/ascii.7:28: warning: cannot select font 'CW'
> man4/console_codes.4:324: warning: table wider than line length minus indentation
> man5/proc_pid_smaps.5:88: warning: table wider than line length minus indentation
> troff:man7/ascii.7:28: warning: cannot select font 'CW'
> SAME
> 
> Thanks again to Brian Inglis for reminding me not to update externally
> generated/sourced pages (bpf-helpers and Paul Eggert's tz project).
> 
> Signed-off-by: "G. Branden Robinson" <g.branden.robinson@gmail.com>
> 
> Regards,
> Branden
> 
> [0] https://lore.kernel.org/linux-man/20231025185341.mqvn7qlm3iby4zgm@illithid/
> [1] https://lists.gnu.org/archive/html/info-gnu/2023-07/msg00001.html
> [2] https://repology.org/project/groff/versions
> [3] You can of course find out how in groff_man(7).


> # Handle simplest cases: ".BR foo (1)" and ".IR foo (1)".
> s/^.[BI]R \(\\%\)*\([.@_[:alnum:]\\-]\+\) (\([1-9a-z]\+\))$/.MR \2 \3/
> # Handle case: trailing punctuation, as in ".IR foo (1),".
> s/^.[BI]R \(\\%\)*\([.@_[:alnum:]\\-]\+\) (\([1-9a-z]\+\))\([^[:space:]]\+\)$/.MR \2 \3 \4/
> # Handle case: leading punctuation, as in ".RI ( foo (1)".
> s/^.R[BI] \(\\%\)*\([^[:space:]]\+\) \([.@_[:alnum:]\\-]\+\) (\([1-9a-z]\+\))\([^[:space:]]\+\)$/\\%\2\\c\n.MR \3 \4 \5/
> # Handle case: 3rd+ arguments or trailing comments.  This case is rare
> # and will require manual fixup if there are 4+ arguments to MR.  Use
> # groff -man -rCHECKSTYLE=1 to have them automatically reported.
> s/^.[BI]R \(\\%\)*\([.@_[:alnum:]\\-]\+\) (\([1-8a-z]\+\))\( .*\)/.MR \2 \3\4/

Recipe applied.  
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=d02c2e2a15b6b9f5c35d1bef150e23cff27372d0>

It's still not in master, so if you want to tweak the commit message,
feel free to suggest an edit.  I'll push tomorrow to master.

Since groff-1.23.0 is already available in most distributions (Gentoo,
Arch, Debian Sid --and Bookworm has backported support for MR--,
Fedora 39), I think it has come the time to apply it.

Cheers,
Alex

-- 
<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 --]

  reply	other threads:[~2024-01-14 18:22 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 [this message]
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

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=ZaQmd0aP1XlFiAKA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.