Update of bug #68888 (group groff):

                 Summary: [troff] rename `rnn` request to `rnr` => [troff]
rename `rnn` request to `rnr` (or `rnnr`?)

    _______________________________________________________

Follow-up Comment #2:

It occurs to me that, with the orthogonality and regularity I am trying to
achieve with request names, `rnr` could reasonably be interpreted as "remove
(number) register", rather than "rename (number) register", by analogy with
`rm`, `rchar`, `rfschar`, and the planned `rev`.

That is, the rule or pattern would seem to be "take the name of the request
that creates an object, and prefix it with `r` to remove the object, or prefix
it with `p` to dump information about it".  With an exception for
macro/strings/diversions, of course, with are created by a variety of
requests, but removed and dumped as things labelled "m".

And `rr` of course breaks the pattern, being very old and restricted to AT&T
_troff_'s two-character request/macro/string/diversion name space.

We could improve the consistency of such a rule by renaming the `de` request
to `dm`, but I fear I'd be tarred and feathered for that idea; while `rnn` is
vanishingly little used, `de` is anything but.


    _______________________________________________________

Reply to this item at:

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

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

Attachment: signature.asc
Description: PGP signature

Reply via email to