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*
On 14/12/19 12:03, Kent Fredric wrote:
> On Sat, 14 Dec 2019 08:16:03 +0100
> Ulrich Mueller wrote:
>
>> 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 ag
On Sat, Dec 14, 2019 at 10:31:06AM +0100, Toralf Förster wrote:
> On 12/14/19 8:16 AM, Ulrich Mueller wrote:
> > 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.
> +1
>
>
> Good idea U
On Sat, 14 Dec 2019 08:16:03 +0100
Ulrich Mueller wrote:
> 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?
> A
On 12/14/19 8:16 AM, Ulrich Mueller wrote:
> 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.
+1
Good idea Ulrich !
The SGR control sequences are annoying in script based grepping of issue
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" # (
