Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.groff.bug > #1732 > unrolled thread

[bug #57510] not all TTY output controls simultaneously available (nroff needs -P)

Started byDave <INVALID.NOREPLY@gnu.org>
First post2020-02-08 15:17 -0500
Last post2020-02-08 15:17 -0500
Articles 1 — 1 participant

Back to article view | Back to gnu.groff.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  [bug #57510] not all TTY output controls simultaneously available (nroff needs -P) Dave <INVALID.NOREPLY@gnu.org> - 2020-02-08 15:17 -0500

#1732 — [bug #57510] not all TTY output controls simultaneously available (nroff needs -P)

FromDave <INVALID.NOREPLY@gnu.org>
Date2020-02-08 15:17 -0500
Subject[bug #57510] not all TTY output controls simultaneously available (nroff needs -P)
Message-ID<mailman.521.1581193047.2412.bug-groff@gnu.org>
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
2020-01-18.




[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:

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

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

[toc] | [standalone]


Back to top | Article view | gnu.groff.bug


csiph-web