[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Groff] Unintended impact of strip.sed on om.tmac-u?

From: G. Branden Robinson
Subject: [Groff] Unintended impact of strip.sed on om.tmac-u?
Date: Tue, 7 Nov 2017 14:18:36 -0500
User-agent: NeoMutt/20170113 (1.7.2)

Hi folks,

I've been inspecting the operation of tmac/strip.sed, and

I noticed that the following substitution:


has an impact outside what I presume is its intension to shorten mdoc
symbol names.  It also does this:

diff -urN STOCK/om.tmac HACKED2/om.tmac
--- STOCK/om.tmac       2017-11-07 13:00:57.786695535 -0500
+++ HACKED2/om.tmac     2017-11-07 13:13:43.424234377 -0500
@@ -5178,7 +5178,7 @@
 .ds cover-type \\$0
 .substring cover-type 0 2
 .ie '\\*[cover-type]'COV' .ds cover-type cover
-.el .ds cover-type cover
+.el .ds cover-type doc-cover
 .tm1 "[mom]: \\$0 at line \\n[.c] of '\\n[.F]' is no longer valid.
 .tm1 "       Leading of \\*[cover-type] MISC items is now set with 
\\*[replacement], which
 .tm1 "       takes an absolute leading value.  Please update your document.

...which makes the conditional a no-op.

All of the other substitutions in strip.sed are agnostic about symbol
names, and work only at the syntactical level.

Maybe mdoc should get its own sed one-liner that runs separately from

I think that would be cheaper than expecting all future contributors to
groff to remember not to name any strings or macros doc-whatever if they
want their macro packages stripped.


Attachment: signature.asc
Description: PGP signature

reply via email to

[Prev in Thread] Current Thread [Next in Thread]