search for: 256color

The terminal programs (xterm, gnome-terminal, etc.) in Fedora have all supported 256 colors for quite a while, so there's a proposal for Fedora to switch them to using "xterm-256color" for $TERM. One drawback would be when you SSH to another host that doesn't have an up-to-date terminal database and doesn't recognize "xterm-256color" (but does know "xterm"). I don't see a way to override $TERM for a particular host in ~/.ssh/config. Also,...

> 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

Hi, I'm using the official 3.6 release binaries for x64 Linux. When compiling with warnings, I don't see any color diagnostics. Explicitly enabling -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any idea why? For what it's worth, I tried compiling LLVM/clang from trunk and color diagnostics work fine by default. Upon further investigation, I saw that the official binaries were not linked against libtinfo: Official binaries: [14:11:05] perry at meepo ~/test zsh▸ ldd /home/perry/opt...

On 17/06/2020 20:06, Noam Bernstein via CentOS wrote: >> On Jun 17, 2020, at 3:02 PM, Phil Perry <pperry at elrepo.org> wrote: >> >> Nothing has changed in this regard for as long as I've been a CentOS user or been involved in the CentOS community. > > This is the essence of the question, to me. I agree that _in_principle_ nothing has changed, and I don't

...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...

...ran for more than 10 years until the > hardware eventually died. EL5... how modern...? from a production application server VM, not internet-connected: [root at c6-2850 ~]# ssh root at 10.1.x.y root at 10.1.x.y's password: Last login: Tue Jan 28 19:53:32 2020 unknown terminal "xterm-256color" unknown terminal "xterm-256color" [root at localhost root]# cat /etc/centos-release CentOS Linux Advanced Server release 2.1AS (Slurm) [root at localhost root]# This one has to be hard reset every day or two (virsh reset rhel2.1) since the bridge to the guest just dies randomly, a...

...at 11:16 AM, Perry Hung <perry at leaflabs.com> wrote: > > I'm using the official 3.6 release binaries for x64 Linux. When compiling > > with warnings, I don't see any color diagnostics. Explicitly enabling > > -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any > idea > > why? > > Which of the release binaries are you using? 3.6 has x86_64 binaries > for Ubuntu, OpenSuSE and Fedora, and they were built by difference > people. > > From your ldd dump, it seems the binary you're using was built without > libtinfo, presu...

...<perry at leaflabs.com> wrote: > >> Hi, >> >> I'm using the official 3.6 release binaries for x64 Linux. When compiling >> with warnings, I don't see any color diagnostics. Explicitly enabling >> -fcolor-diagnostics works fine. I have TERM set to xterm-256color. Any idea >> why? >> >> For what it's worth, I tried compiling LLVM/clang from trunk and color >> diagnostics work fine by default. >> >> Upon further investigation, I saw that the official binaries were not >> linked against libtinfo: >> >>...

Hi, I have a KVM host running ubuntu 18.04 with libguestfs-tools version 1.36.13-1ubuntu3.3 installed from the Ubuntu's repo and when I try to use virt-cat for example on a VM it fails with: libguestfs: error: appliance closed the connection unexpectedly. > libguestfs: error: guestfs_launch failed. After doing "export LIBGUESTFS_DEBUG=1 LIBGUESTFS_TRACE=1" and running the

...=channel0,name=org.libguestfs.channel.0 \ > -append 'panic=1 console=ttyS0 edd=off udevtimeout=6000 udev.event-timeout=6000 no_timer_check printk.time=1 cgroup_disable=memory usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm-256color' > libguestfs: responding to serial console Device Status Report > \x1b[1;256r\x1b[256;256H\x1b[6n > Google, Inc. > Serial Graphics Adapter 03/05/17 > SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (generic@generic) Sun, 05 Mar 2017 16:09:17 +0100 > Term: 80x24 > 4...

...ibguestfs.channel.0 \ > > -append 'panic=1 console=ttyS0 edd=off udevtimeout=6000 > udev.event-timeout=6000 no_timer_check printk.time=1 cgroup_disable=memory > usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=/dev/sdb > selinux=0 guestfs_verbose=1 TERM=xterm-256color' > > libguestfs: responding to serial console Device Status Report > > \x1b[1;256r\x1b[256;256H\x1b[6n > > Google, Inc. > > Serial Graphics Adapter 03/05/17 > > SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (generic@generic) > Sun, 05 Mar 2017 16:09:17...

...ardev=channel0,name=org.libguestfs.channel.0 \ -append 'panic=1 console=ttyS0 edd=off udevtimeout=6000 udev.event-timeout=6000 no_timer_check printk.time=1 cgroup_disable=memory usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm-256color' libguestfs: responding to serial console Device Status Report \x1b[1;256r\x1b[256;256H\x1b[6n Google, Inc. Serial Graphics Adapter 06/09/14 SGABIOS $Id: sgabios.S 8 2010-04-22 00:03:40Z nlaredo $ (mockbuild@) Mon Jun 9 21:33:48 UTC 2014 Term: 80x24 4 0 SeaBIOS (version seabios-1.7.5-8.el7) Bo...

...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* Ema...

...alport,chardev=channel0,name=org.libguestfs.channel.0 \ > > -append 'panic=1 mem=500M console=ttyAMA0 udevtimeout=6000 > > udev.event-timeout=6000 no_timer_check acpi=off printk.time=1 > > cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 > > TERM=xterm-256color' > > qemu-system-arm: Warning: global kvm-pit.lost_tick_policy has invalid class > > name > > Alarm clock The main problem is that the original poster's kernel doesn't boot on top of qemu. I can't see from the logs what kernel they are trying to use, but that'...

...lare -x OLDPWD declare -x PATH="/usr/local/bin:/bin:/usr/bin:/usr/local/sbin:/usr/sbin:/sbin:/home/xxxx/bin:/opt/current/maven/bin:/opt/current/java/bin" declare -x PWD="/home/xxxx" declare -x SHELL="/bin/bash" declare -x SHLVL="1" declare -x TERM="xterm-256color" declare -x USER=?xxxx" -bash: PATH: command not found I have tried to rectify the issue using the usermod and chsh commands with no success. Is there anything else that I can do to get rid of this message? Kind Regards Leon

...len 4 debug2: mux_master_process_alive_check: channel 1: alive check debug3: mux_client_request_alive: done pid = 806 debug3: mux_master_read_cb: channel 1 packet type 0x10000002 len 57 debug2: mux_master_process_new_session: channel 1: request tty 1, X 0, agent 0, subsys 0, term "rxvt-unicode-256color", cmd "", env 0 debug3: mm_receive_fd: recvmsg: Resource temporarily unavailable mm_receive_fd: recvmsg: expected received 1 got 0 mux_master_process_new_session: failed to receive fd 0 from slave debug1: channel 1: mux_rcb failed debug2: channel 1: zombie debug2: channel 1: gc: noti...

> On 2020-05-31 15:59, Antony Stone wrote: > On Sunday 31 May 2020 at 15:44:46, Fourhundred Thecat wrote: > > "%Cn[;n] - Change terminal foreground (and optional background) color to > specified A full list of colors may be found in include/asterisk/term.h" > > So, try: > > export ASTERISK_PROMPT="%C31[%H]: " > > (I got 31 from reading the

...-device virtserialport,chardev=channel0,name=org.libguestfs.channel.0 \ > -append 'panic=1 mem=500M console=ttyAMA0 udevtimeout=6000 > udev.event-timeout=6000 no_timer_check acpi=off printk.time=1 > cgroup_disable=memory root=/dev/sdb selinux=0 guestfs_verbose=1 > TERM=xterm-256color' > qemu-system-arm: Warning: global kvm-pit.lost_tick_policy has invalid class > name > Alarm clock > > > root@cubietruck:~# virt-host-validate > QEMU: Checking for hardware virtualization > : WARN (Only emulated CPUs are available, performance will be significantly &g...

...ardev=channel0,name=org.libguestfs.channel.0 \ -append 'panic=1 console=ttyS0 edd=off udevtimeout=6000 udev.event-timeout=6000 no_timer_check printk.time=1 cgroup_disable=memory usbcore.nousb cryptomgr.notests tsc=reliable 8250.nr_uarts=1 root=/dev/sdb selinux=0 guestfs_verbose=1 TERM=xterm-256color' nbdkit: debug: accepted connection nbdkit: debug: /home/rjones/d/nbdkit/plugins/nbd/.libs/nbdkit-nbd-plugin.so: open readonly=0 nbdkit: debug: accepted connection nbdkit: debug: /home/rjones/d/nbdkit/plugins/nbd/.libs/nbdkit-nbd-plugin.so: open readonly=0 nbdkit: debug: accepted connection nbd...

When converting from a single transaction to a linked list, I forgot to free the storage for each member of the list. Reported-by: Richard W.M. Jones <rjones at redhat.com> Fixes: 7f5bb9bf13f041ea7702bda557d9dd668bc3423a Signed-off-by: Eric Blake <eblake at redhat.com> --- I'm still not sure why 'make check' passes while 'make check-valgrind' fails for