[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #57510] not all TTY output controls simultaneously available (nroff
[bug #57510] not all TTY output controls simultaneously available (nroff needs -P)
Sat, 8 Feb 2020 15:17:24 -0500 (EST)
Mozilla/5.0 (X11; Linux i686; rv:45.0) Gecko/20100101 Firefox/45.0
Follow-up Comment #14, bug #57510 (project groff):
[comment #12 comment #12:]
> Take 2 attached.
The only attachment I can see is the original patch, file #48243, added
[comment #5 comment #5:]
> I strongly oppose deprecating -c. As i repeatedly said
> before, i consider it superior to SGR output...
I apologize if I was unclear. I was not suggesting making the functionality
of -c (or -h) unobtainable. But with the addition of a -P flag, -c merely
becomes an alias for -P-c, and -h for -P-h. Certainly for backward
compatibility, bare -c and -h will have to be supported for some time to come.
My only question is, looking toward the (possibly distant) future, does it
make sense to nudge users toward the more generic and flexible -P framework
for passing all options to grotty?
> Reusing options for a different purpose isn't a particularly
> bright idea. At least, a very long time should pass between
> deprecation and reuse. The point of deprecating stuff isn't
> to free up namespace for reuse. The point is to make the
> user interface smaller and simpler.
Agree with all this, which is why I tongue-in-cheekly invoked 2034 (though
perhaps 14 years doesn't seem like "a very long time" to 50-year-old
software). But yes, my primary motive is to (eventually) remove the
redundancy of two different mechanisms for specifying the same thing.
Reply to this item at:
Message sent via Savannah
- [bug #57510] not all TTY output controls simultaneously available (nroff needs -P),