On Tue, 29 Aug 2023, Dennis Williamson wrote:
> I've found https://gist.github.com/sdeaton2/8450564 but I'm looking for
> something more complete.
>
> Does anyone know of such a thing?
> A) Use tput or an ANSI library to obtain the code sequences based on the TERM setting instead of hard coding them.
It's not my code -- I just wanted to be sure my terminal is doing "the
right thing" before I get dozens of "works on my device" responses. I'm
using BSD rather than linux, which people often wrongly poke as the
problem, but an xterm should still be an xterm.
> B) See vttest https://invisible-island.net/vttest/vttest.html for xterm tests
vttest seems to be a tool to regression-test compatibility with the
venerable vt100 standard, but it at least confirms that my iTerm and
screen setup do "The right thing" with regard to bold text, so I'm more
convinced that someone hardcoded a value and forgot to embed the \003
correctly. (Especially considering color works in the same program).
I've reported a bug on github and can call it the end of the day
It would be neat if vttest also supported more modern xterm features like
image embedding, custom composed characters, ligatures, 256-color support,
foreign characters, right-to-left encoding, double-wide characters, or
even Emoji.
At the very least, it showed me that my terminal doesn't support blinking
text -- which might be a good thing!
Best,
-Dan
--
--------Dan Mahoney--------
Techie, Sysadmin, WebGeek
Gushi on efnet/undernet IRC
FB: fb.com/DanielMahoneyIV
LI: linkedin.com/in/gushi
Site: http://www.gushi.org
---------------------------
Option 4 in the first menu is "Test of double-sized characters". Terminal.app on MacOS (at least on mine which is Ventura) supports blinking text, for better or worse. I do miss HTML <blink> though. ;-)
-- Visit
serverfault.com to get your system administration questions answered.