[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #61710] [me] $v and $V are in the wrong namespace
From: |
Dave |
Subject: |
[bug #61710] [me] $v and $V are in the wrong namespace |
Date: |
Wed, 22 Dec 2021 19:07:10 -0500 (EST) |
User-agent: |
Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0 |
Follow-up Comment #2, bug #61710 (project groff):
[comment #1 comment #1:]
> I think it would be straightforward to extend `sz` to accept an
> optional second argument setting the vertical spacing. The macro
> can check its own context for whether it should set $v or $V.
I like the thinking outside the box!
Unfortunately, this proposal isn't congruent with the way -me operates
regarding other type-size-related matters.
In general, -me relies on the user to set registers (pp, sp, fp, et al.) to
make persistent changes to the type size. The .sz macro is specifically
documented as _not_ persistent: -me frequently automatically resets the type
size to the values stored in the appropriate register -- and, at the same
time, the line spacing to that stored in $v -- clobbering whatever was set by
the last call to .sz. (The .sz section of the reference manual lists typical
situations where this happens.) Making one of its parameters persistent and
the other not would be an odd design.
So exposing $v and $V to the user as registers, rather than as macro
parameters, is in line with the way all these others are handled. It's only
their names that aren't.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61710>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/