From: Thomas Wolff <towo@towo.net>
To: cygwin-apps@cygwin.com
Subject: Re: [ITP] italic-man
Date: Sat, 10 Aug 2019 21:39:00 -0000 [thread overview]
Message-ID: <7290fd25-e1be-93d3-87ca-0b7c9422155b@towo.net> (raw)
In-Reply-To: <d55c2e25-8e83-cecf-b238-ee4152689be7@towo.net>
Am 10.08.2019 um 11:07 schrieb Thomas Wolff:
> Am 09.08.2019 um 22:51 schrieb Brian Inglis:
>> On 2019-08-09 13:31, Thomas Wolff wrote:
>>> Am 09.08.2019 um 20:56 schrieb Achim Gratz:
>>>> Jon Turney writes:
>>>>> This gets a GTG from me.
>>>>> I believe that according to our stated procedures additional
>>>>> approvals
>>>>> are required, because this package is unique to cygwin.
>>>> I'm not sure I remember correctly from when the discussion went on the
>>>> first time, but wasn't there some mumbling about this partly going
>>>> into
>>>> groff? If that's still the case, remind me what this would entail and
>>>> I'll look into it.
>>> There are multiple ways of activating the feature (also described in
>>> the man page).
>>> The previous strategy placed a shell script wrapper "groff" aside
>>> groff, so the
>>> groff script and groff.exe would coexist in /bin. This was tricky to
>>> install and
>>> particularly it reportedly did not survive a package update of groff.
>>> The new approach does not use this wrapper anymore. Instead it
>>> redirects nroff
>>> to the package-supplied iroff script by configuration in
>>> /etc/man_db.conf.
>> There's also use of the undocumented LESS_TERMCAP_... with
>> GROFF_NO_SGR env vars
>> (see attached - must be sourced from profile or rc) to remap bold,
>> underline,
>> etc. into italic and/or colour, or whatever else you want to change,
>> in all less
>> output.
> So (without my package) LESS_TERMCAP_us=$(tput sitm) man ls
> should have the same effect? Cannot reproduce. And what does
> GROFF_NO_SGR do?
Ah, this works:
GROFF_NO_SGR= LESS_TERMCAP_us="^[[3m" LESS_TERMCAP_ue="^[[23m" man ls
no matter what the value of GROFF_NO_SGR is. Which tool in the `man`
chain interprets the latter?
Value-added of my package:
* automatic injection into the `man` pipe
* terminal-dependent enabling, after checking the terminal type
next prev parent reply other threads:[~2019-08-10 21:39 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-28 6:01 Thomas Wolff
2019-08-09 12:59 ` Jon Turney
2019-08-09 15:07 ` Ken Brown
2019-08-09 18:56 ` Achim Gratz
2019-08-09 19:31 ` Thomas Wolff
2019-08-09 20:51 ` Brian Inglis
2019-08-10 9:07 ` Thomas Wolff
2019-08-10 21:39 ` Thomas Wolff [this message]
2019-08-10 22:29 ` Brian Inglis
2019-08-11 9:33 ` Thomas Wolff
2019-08-11 16:17 ` Achim Gratz
2023-01-21 17:04 Thomas Wolff
2023-02-16 18:59 ` Jon Turney
2023-02-16 19:17 ` Thomas Wolff
2023-06-21 21:45 ` Thomas Wolff
2023-06-25 13:36 ` Jon Turney
2023-06-25 13:59 ` Thomas Wolff
2023-06-25 16:02 ` ASSI
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=7290fd25-e1be-93d3-87ca-0b7c9422155b@towo.net \
--to=towo@towo.net \
--cc=cygwin-apps@cygwin.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).