You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Looking at the above, h=$(oxend print_height | tail -n 1) ought to be a trivial operation, but it's not. I have to pipe oxend's output through sed or similar to de-ANSI-fy it. Otherwise:
oxend should respect $TERM (e.g. TERM=dumb) and use isatty(3) before deciding to use ANSI control sequences in its output.
At the very least, can we please have a --no-ansi flag or something similar for the purposes of scripting?
The text was updated successfully, but these errors were encountered:
ianmacd
changed the title
oxend's use of ANSI escape sequences is scripter-unfriendly.
oxend uses ANSI escape sequences without regard for $TERM or isatty(3)
Jul 24, 2022
Describe the bug
Looking at the above,
h=$(oxend print_height | tail -n 1)
ought to be a trivial operation, but it's not. I have to pipeoxend
's output throughsed
or similar to de-ANSI-fy it. Otherwise:oxend
should respect$TERM
(e.g.TERM=dumb
) and useisatty(3)
before deciding to use ANSI control sequences in its output.At the very least, can we please have a
--no-ansi
flag or something similar for the purposes of scripting?The text was updated successfully, but these errors were encountered: