The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Leah Neukirchen <leah@vuxu.org>
Cc: "Jacobson, Doug W [E CPE]" <dougj@iastate.edu>,
	"tuhs@tuhs.org" <tuhs@tuhs.org>,
	groff@gnu.org
Subject: [TUHS] Re: Old troff files (1988-2007)
Date: Tue, 8 Oct 2024 01:45:08 -0500	[thread overview]
Message-ID: <20241008064508.vtcvijqmedztrfeb@illithid> (raw)
In-Reply-To: <87ploc2chj.fsf@vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 1508 bytes --]

Hi Leah,

At 2024-10-07T16:50:48+0200, Leah Neukirchen wrote:
> "G. Branden Robinson" <g.branden.robinson@gmail.com> writes:
> > Anton Shepelev wrote a summary I find admirably concise and blunt:
> >
> > "`grotty' is not an appendix to a pager, but a program for printing
> > direct to the terminal.  Most terminals support those basic ANSI
> > control sequences, and many console programs freely use them.  If a
> > pager cannot transparently forward them to the terminal, it is a
> > problem of the pager, not of `grotty', and having a broken -man
> > configuration by default to just to appease `less' is stupid."
> 
> I don't see the problem, less supports -R for the last 25 years...

Yeah.  People's ire seems to rise from the fact that grotty's default is
to assume SGR support and less's default is to not interpret SGR.

I would prefer that `-R` were less's default; that would better serve
the larger proportion of ECMA-48 video terminals using the pager versus
those using it with (an emulator of) hardcopy terminals.

Whatever transition process needs to commence for that to happen, I
think it should.

But in the meantime it's no great effort for me (nor for most people) to
alias 'less' to 'less -R', write a shell function to do similarly, or
just type three more characters.

(For those requiring accessibility assistance, shell aliases and
functions, programmable key bindings, and similar should serve as they
do the merely impatient.)

Regards,
Branden

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-10-08  6:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-04 21:42 [TUHS] " Jacobson, Doug W [E CPE] via TUHS
2024-10-04 21:50 ` [TUHS] " Lyndon Nerenberg (VE7TFX/VE6BBM)
2024-10-04 21:52   ` Jacobson, Doug W [E CPE] via TUHS
2024-10-04 22:10     ` Bakul Shah via TUHS
2024-10-04 23:01     ` Clem Cole
2024-10-04 23:16       ` Clem Cole
2024-10-05  0:14 ` G. Branden Robinson
2024-10-05  4:09   ` Peter Yardley
2024-10-05 13:14   ` Clem Cole
2024-10-05 22:22     ` G. Branden Robinson
     [not found]       ` <CAC20D2NgmzDxhQu5P5hjrZ3ciSv=KayiUg8GwsFRpu0wPasprw@mail.gmail.com>
2024-10-06  5:53         ` [TUHS] Why groff ms doesn't completely support historical documents G. Branden Robinson
2024-10-06 12:54       ` [TUHS] Re: Old troff files (1988-2007) Jaap Akkerhuis
2024-10-06 15:11         ` G. Branden Robinson
2024-10-06 16:21           ` Ron Natalie
2024-10-09 21:02             ` Ron Natalie
2024-10-07 14:50       ` Leah Neukirchen
2024-10-08  6:45         ` G. Branden Robinson [this message]
2024-10-08 10:33           ` Jacobson, Doug W [E CPE] via TUHS
2024-10-08 10:49             ` G. Branden Robinson
2024-10-08 11:24               ` Jacobson, Doug W [E CPE] via TUHS
2024-10-16 21:40 ` Anton Shepelev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241008064508.vtcvijqmedztrfeb@illithid \
    --to=g.branden.robinson@gmail.com \
    --cc=dougj@iastate.edu \
    --cc=groff@gnu.org \
    --cc=leah@vuxu.org \
    --cc=tuhs@tuhs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).