Bug 203266 – sys-apps/baselayout-2.0.0_rc6: einfo/ewarn/eerror don't interpret "\n", "\t" etc.

• Status: RESOLVED WONTFIX
• Product: Gentoo Linux

[Description Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-12-24 23:57:32 UTC]

sys-apps/baselayout-2.0.0_rc6: einfo/ewarn/eerror don't interpret "\n", "\t" etc.
They were interpreted by sys-apps/baselayout-1.12*.

[Comment 1 Roy Marples 2007-12-28 20:13:11 UTC]

einfo and friends are not meant to interpret \n.
You should use a new einfo call for a new line.

You could try prefixing the command with eval so that shell interprets the escaped chars correctly.

[Comment 2 Arfrever Frehtes Taifersar Arahesis (RETIRED) 2007-12-28 21:42:20 UTC]

(In reply to comment #1)
> einfo and friends are not meant to interpret \n.

Why?
And what do you think about "\t" and "\e[XXm"?

> You should use a new einfo call for a new line.
> 
> You could try prefixing the command with eval so that shell interprets the
> escaped chars correctly.

There are also some scripts which rely on old, correct behaviour.
Example:
/usr/sbin/ruby-config -l

[Comment 3 Roy Marples 2007-12-28 22:47:39 UTC]

Created attachment 139543 [details, diff]
ruby-config should use eindent

which is also compatible with baselayout-1

[Comment 4 Roy Marples 2007-12-28 22:53:07 UTC]

(In reply to comment #2)
> (In reply to comment #1)
> > einfo and friends are not meant to interpret \n.
> 
> Why?
> And what do you think about "\t" and "\e[XXm"?

Well, Gentoo has always coded for one einfo per line on the whole. That is why there is einfon, which is NOT to add a newline. That is the intent, and we can use this logic for more intelligent display in the future.

Also, embedded escape codes are bad, as not all consoles support the same features and sometimes use different codes.

[Comment 5 SpanKY 2008-01-01 18:30:09 UTC]

nothing to do for baselayout-2