Re: [yocto] strange formatting of command output on core-image-base

["Khem Raj" <raj.khem@gmail.com>]

On 5/20/20 3:23 AM, stefan.wenninger@evopro-ag.de wrote:
> Hi,
> I recently switched form an image based on fsl-image-qt5 to one based on 
> core-image-base.
> The new image works fine in every regard except that the output of some 
> commands looks weird.
> 
> I have attached the output of commands "nmcli" and "systemctl status 
> dbus". Once executed on the fsl-image-qt5 based system and once on the 
> core-image-base based system (_weird.txt).
> There are two main points I gather from that weird output:
> 1. There are some codes like "[[32m"+"[[0m" or "[[0;1;32m"+"[[0m", which 
> I assume are colour codes, that are printed and not applied.
> 2. The output appears to be opened in a vi-like editor?! It clears and 
> fills the entire terminal page and seems to display an input mode at the 
> bottom.
> 
> Both of these aspects are non-existent on the fsl-image-qt5 based 
> system. There, colours are displayed normally and the output is just 
> printed right beneath my command call.
> 
> I have discovered that I can get these two commands to work properly on 
> the core-image-base based system, if I pipe their output into cat: 
> "nmcli | cat".
> 
> My assumption for the colour codes is that, the core-image-base system 
> uses a different text encoding, or a different style of colour codes and 
> therefore does not recognize the ones presented by nmcli.
> I have tried to install the ttf-dejavu-* fonts that are present on the 
> fsl-image-qt system. I also verfied that both systems seem to be using 
> POSIX as their LANG setting ("locale" produces the same output on both).
> I have no idea why the output is presented in what seems to be a vi 
> editor though. Both systems have their EDITOR variable set to "vi".
> 
> Am I missing some kind of package or setting in my image?
> 
> I am at my wits' end and would greatly appreciate anyone trying to shed 
> some light on what is going on here.
> Stefan Wenninger
> 

Its perhaps some of  busybox applets like cat etc. Try 
core-image-full-cmdline and see if its any better.