[bug #61710] [me] $v and $V are in the wrong namespace

[G. Branden Robinson]

Follow-up Comment #11, bug #61710 (project groff):

[comment #7 comment #7:]
> [comment #6 comment #6:]
> > I propose that we ditch $v/$V for 1.23.0-rc2, and for that
> > release candidate, actually put out some release notes this
> > time.
> 
> That's reasonable.  But does ditching $v and $V also
> necessitate ditching support for $r and $R, as the latter are
> essentially aliases of the former?

No, but it is not clear to me why the $[vV] registers were
introduced to groff in the first place.  I guess just to loosen
the conditions that cause $[rR] to have no effect at all.

> > That leaves the original question of `sz` behavior.
> 
> As long as we're committing to using registers as the approved
> mechanism for specifying leading, we've decoupled the .sz
> issue from this one: .sz needn't change in order to reorganize
> the registers.  (The original proposal to change .sz was based
> on avoiding exposing registers for this functionality.)
> 
> Any changes to .sz can then be considered as a separate
> enhancement.  (At least, from a UI perspective.  From a coding
> perspective, they may still be coupled more tightly than that,
> and you may want to consider the issues in tandem.)

Right.  I want to get the most sensible UI I can within the
constraints of maintainability, and then worry about the
implementation.  (One can misjudge such things, of course, and
have to go back to the UI question with an "I'm sorry, that
turned out to be intractable".)


    _______________________________________________________

Reply to this item at:

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

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