asterisk users - Jun 2020 - CLI color prompt

> On 2020-05-31 18:39, Ira wrote:
>
> I typed this at the terminal prompt:  export
ASTERISK_PROMPT="%C31[%H]: "
>
> Typing at the same place:  echo $TERM  returns xterm
>
> And now I have colored prompts at the Asterisk command line, so I can
> assure you it can work. Kind of cool, 14 years using Asterisk and
> because of your question, I now have colored prompts.
>
> Do I have to do something to make sure that ASTERISK_PROMPT lives
> through a reboot?
I would add the export to .bashrc/.zshrc or whatever shell you are using

why does it not work for me?
My terminal clearly supports 256 colors.

Hi,

I had posted this a few hours ago, but got caught in moderation for 
size.  I trimmed down the pic and attached.

I am on an Ubuntu 16 workstation, in an Ubuntu terminal window, ssh'ed 
to the PBX (amazon instance).  You can see my term type matches yours.

I really don't know why yours doesn't work.  Perhaps you can tell us 
what your terminal emulator is, what you are running it on, etc.  
Whatever it is, it isn't properly interpreting the escape codes for 
xterm-256color.  You could possibly try some different terminal types, 
but this is an odd situation if the remote shell (is it remote?) can't 
determine your termtype.  This is pretty ancient code.

j


	*Jeff LaCoursiere*
STRATUSTALK, INC. / CTO

Phone: 	*+1 703.496.4990 x108*
Mobile: 	*+1 815.546.6599*
Email: 	*jeff at stratustalk.com* <mailto:jeff at stratustalk.com>
Website: 	*https://www.stratustalk.com*
Address: 	*One Freedom Square
13th Floor
Reston, VA 20190*

<https://www.facebook.com/jeff.lacoursiere> 
<https://linkedin.com/in/jeff-lacoursiere-884361> 
<https://www.twitter.com/stratustalk>

On 5/31/20 11:42 AM, Fourhundred Thecat wrote:
>> On 2020-05-31 18:39, Ira wrote:
>>
>> I typed this at the terminal prompt:  export
ASTERISK_PROMPT="%C31[%H]: "
>>
>> Typing at the same place:  echo $TERM  returns xterm
>>
>> And now I have colored prompts at the Asterisk command line, so I can
>> assure you it can work. Kind of cool, 14 years using Asterisk and
>> because of your question, I now have colored prompts.
>>
>> Do I have to do something to make sure that ASTERISK_PROMPT lives
>> through a reboot?
> I would add the export to .bashrc/.zshrc or whatever shell you are using
>
> why does it not work for me?
> My terminal clearly supports 256 colors.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200531/475283a1/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: colorasterisk.png
Type: image/png
Size: 22547 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200531/475283a1/attachment.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: jeff.vcf
Type: text/x-vcard
Size: 321 bytes
Desc: not available
URL:
<http://lists.digium.com/pipermail/asterisk-users/attachments/20200531/475283a1/attachment.vcf>

> On 2020-05-31 19:26, Jeff LaCoursiere wrote:
> Hi,
>
> I really don't know why yours doesn't work.  Perhaps you can tell
us
> what your terminal emulator is, what you are running it on, etc.
> Whatever it is, it isn't properly interpreting the escape codes for
> xterm-256color.  You could possibly try some different terminal types,
> but this is an odd situation if the remote shell (is it remote?) can't
> determine your termtype.  This is pretty ancient code.
my terminal emulator is terminator, I also tried xterm (same result)

and echo $TERM gives me:
xterm-256color

My system is Debian Buster, but not sure if that is relevant

what terminal emulator are you using ?

On 31.05.20 at 19:26 Jeff LaCoursiere wrote:
> Hi,
> 
> I had posted this a few hours ago, but got caught in moderation for size. 
I trimmed down the pic and attached.
> 
> I am on an Ubuntu 16 workstation, in an Ubuntu terminal window, ssh'ed
to the PBX (amazon instance).  You can see my term type matches yours.
Same problem here (asterisk 16.x / CentOS 7).
# echo $TERM
xterm-256color

=> CLI prompt looks the same as described by the OP:
[1;31m[myhostname]:

But to make it even more strange: colored output on the asterisk CLI works
pretty fine for DEBUG output like
core set debug 5

Maybe some link time functionality not enabled? Don't know ... . Or some
other additional asterisk switch needed?


Thanks
Regards
Michael