Re: [gentoo-dev] Output of ANSI escape sequences in ebuilds

[William Hubbs]

On Sat, Dec 14, 2019 at 08:16:03AM +0100, Ulrich Mueller wrote:
> Some ebuilds output SGR control sequences (formerly known as ANSI escape
> sequences) to the terminal, i.e., they do things like:
>
>   echo -e "\033[1m${@}\033[0m"
>   einfo "Fetching \e[1m${r}\e[22m ..."
>   ewarn "\033[1;33m**************************************************\033[00m"
>   echo -ne "\a"   # (not actually an ANSI escape sequence)
>
> These prevent NOCOLOR in make.conf or emerge --color=n from working
> correctly, and I guess they are also problematic from an accessibility
> point of view.
>
> Are there any objections against removing these sequences from strings?
> AFAICS, they are used by less than ten packages, and one eclass.

I just found another place that uses them very heavily. I don't know if
it is part of cargo.eclass, or if it is a bug in /usr/bin/ebuild, but
I'm working on an ebuild and found that if I run:

$ ebuild foobar.ebuild compile >& output

that output file is full of ansi sequences even though I have
NOCOLOR=yes in make.conf.

Thanks,

William