From: Larry McVoy <lm@mcvoy.com>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: cctalk <cctalk@classiccmp.org>,
The Unix Heritage Society <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Seeking wisdom from Unix Greybeards
Date: Wed, 25 Nov 2020 09:38:14 -0800 [thread overview]
Message-ID: <20201125173814.GB9589@mcvoy.com> (raw)
In-Reply-To: <9c1595cc-54a1-8af9-0c2d-083cb04dd97c@spamtrap.tnetconsulting.net>
man 1 tput
is what I use.
On Wed, Nov 25, 2020 at 10:14:55AM -0700, Grant Taylor via TUHS wrote:
> Hi,
>
> As I find myself starting yet another project that that wants to use ANSI
> control sequences for colorization of text, I find myself -- yet again --
> wondering if there is a better way to generate the output from the code in a
> way that respects TERMinal capabilites.
>
> Is there a better / different control sequence that I can ~> should use for
> colorizing / stylizing output that will account for the differences in
> capabilities between a VT100 and XTerm?
>
> Can I wrap things that I output so that I don't send color control sequences
> to a TERMinal that doesn't support them?
>
>
>
> --
> Grant. . . .
> unix || die
>
--
---
Larry McVoy lm at mcvoy.com http://www.mcvoy.com/lm
next prev parent reply other threads:[~2020-11-25 17:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-25 17:14 Grant Taylor via TUHS
2020-11-25 17:22 ` Ralph Corderoy
[not found] ` <20201126145134.GB394251@mit.edu>
2020-11-26 21:48 ` steffen
2021-02-10 18:57 ` Greg A. Woods
2021-02-10 22:26 ` Clem Cole
2021-02-24 22:20 ` Steffen Nurpmeso
2020-11-26 21:59 ` dave
2020-11-25 17:38 ` Larry McVoy [this message]
2020-11-25 18:00 ` Steffen Nurpmeso
2020-11-25 20:03 ` Steffen Nurpmeso
[not found] ` <CACYmRNAtdJu0ui=CgrEcWH6J3uikCh0=aCLNvk0+V29rypDBAg@mail.gmail.com>
[not found] ` <71fdfa2e-1483-4985-3f55-6760b3a84ec0@gmail.com>
[not found] ` <20201126182937.GN9589@mcvoy.com>
2020-11-26 23:14 ` erc
2020-11-26 23:23 ` lm
[not found] <20201126183746.DD93218C087@mercury.lcs.mit.edu>
[not found] ` <7DBB40AE-259D-494E-8ABF-2FE4D47F4052@iitbombay.org>
2020-11-26 19:02 ` lars
2020-11-26 21:56 ` steffen
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=20201125173814.GB9589@mcvoy.com \
--to=lm@mcvoy.com \
--cc=cctalk@classiccmp.org \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.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).