Follow-up Comment #5, bug #68908 (group groff):

At 2026-11-14T12:10:44-0500, Dave wrote:
> Follow-up Comment #3, bug #68908 (group groff):
> It probably goes without saying, but I have no objection to a new
> predefined string or register allowing the document to learn version
> information beyond x.y.z.  I don't personally want such a thing, but I
> can see its usefulness, especially in a groff that ships with a distro
> that has modified it.
>
> But the historically numeric .Y register is not the place for this.

I made no deliberate change in this respect.  If I meant for `.Y` to
become "string-valued", I would have (assuming I kept my wits about me)
committed a documentation change saying so.

See, e.g., _groff_(7):


     \n[.ev]        Name of environment (string‐valued).
...
     \n[.F]         Name of input file (string‐valued); see lf.
     \n[.fam]       Name of the environment’s default font family
                    (string‐valued).
     \n[.fn]        Resolved (and translated, as applicable) name of
                    font selected in the environment (string‐valued);
                    see ft and \f.
...
     \n[.vpt]       Vertical position traps are enabled (Boolean‐
                    valued).
     \n[.w]         Width of last glyph formatted in the environment.
     \n[.warn]      Sum of the numeric codes of enabled warning
                    categories.
     \n[.x]         Major version number of the running troff formatter.
     \n[.y]         Minor version number of the running troff formatter.
     \n[.Y]         Revision number of the running troff formatter.
     \n[.z]         Name of diversion (string‐valued).  Empty if output
                    is directed to the top‐level diversion.


> It breaks historical usage of the register, which defeats the whole
> purpose of _having_ a mechanism to test the version.

Inadvertent, but as I noted in my previous comment, in a "dirty tree",
anything might go wrong, so I don't regard this problem as pressing.
That doesn't mean that someone else can't work on it.

In contrast, if you come up with a defect that permits non-numeric
content into the `.Y` register in a "clean" working copy, I'm intensely
interested to know about it--and inclined to bean it with my chancla.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?68908>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to