News for hackers. Stuff that matters.

A comment on CLI Guidelines – A guide to help you write better command-line programs. Parent comment

Re:CLI Guidelines – A guide to help you write better command... by antientropic on Saturday December 05, 2020 @06:18AM (#25313656)
No, don't bother with terminfo. It just gives you support for terminals that haven't been in use since the Apollo program. Nowadays it's perfectly fine to use ANSI escapes directly, which are, after all, a standard.
[ Parent | on HN ]
Re:CLI Guidelines – A guide to help you write better command... by lokedhs on Saturday December 05, 2020 @06:51AM (#25313863)
At the very least, use isatty() to check whether the output is actually to a terminal before polluting the log files.
[ Parent | on HN ]
Re:CLI Guidelines – A guide to help you write better command... by account42 on Monday December 07, 2020 @06:55AM (#25331310)
isatty and checking for TERM=dumb are sensible (as well as flags to enable/disable colors). Terminfo however is a meh depencency and since common tools (e.g. git) don't bother either there is no point in anything beyond that.
[ Parent | on HN ]