Linux console! I used to work on computers with a console, but that was way back! Mainframes likely still have them, even though they run UNIX under the covers. So I should avoid using the PC monitor? Get a terminal, install ssh for login, and come in from either a terminal (who has one any more) or different host to do simple shell programming and xwindows copy/paste?
I just want a terminal without any counterproductive behaviors, like the xterm/vt100 without color escape sequences, not that I ever wanted grep, less, or vi with colored text for anything -- reverse video highlighting was quite sufficient. Can you recommend a way to get back to a terminal with text I can trust? -----Original Message----- From: Thomas Dickey <1983...@bugs.launchpad.net> To: dgpick...@aol.com Sent: Tue, Aug 2, 2022 4:29 am Subject: [Bug 1983276] Re: xterm processing grep color loses char at end of line If you don't like that, you should (see the FAQ) avoid using Linux console as well. -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1983276 Title: xterm processing grep color loses char at end of line Status in xterm package in Ubuntu: Invalid Bug description: Note the xterm displays "freshcla_cron.log" but the strace says the write data held "fresh\33[01;31m\33[Kclam\33[m\33[K_cron.log", no missing m. (My trussxx is a strace with options and vi wrapper, evolved since I left Solaris and its 'truss'. My pse is a ps -ef|grep $@. I am up to date on Ubuntu 20.04 LTS patches.): $ crontab -l|(sleep 2 ; grep clam)& trussxx -p $! [1] 23978 strace: Process 23978 attached strace: Process 23985 attached 30 23 * * * /usr/bin/freshclam --datadir=/home/dgp/.clamtk/db --log=/home/dgp/.clamtk/db/freshclam.$(/bin/date +\%b-\%d-\%Y).log >/home/dgp/.clamtk/db/freshcla_cron.log 2>&1 ; /usr/local/bin/clamdscan --reload --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" >>.clamtk/history/clamscan.log 2>&1 ; if [ `fuser .clamtk/history/clamscan.log 2>/dev/null` = "" ]; then echo Still running >>.clamtk/history/clamscan.log ; else /usr/local/bin/clamdscan --quiet --multiscan --fdpass --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" / >>.clamtk/history/clamscan.log 2>&1 ; fi # freshclam update and clam-scan =================================== 23985 write(1, "30 23 * * * /usr/bin/fresh\33[01;31m\33[Kclam\33[m\33[K --datadir=/home/dgp/.\33[01;31m\33[Kclam\33[m\33[Ktk/db --log=/home/dgp/.\33[01;31m\33[Kclam\33[m\33[Ktk/db/fresh\33[01;31m\33[Kclam\33[m\33[K.$(/bin/date +\\%b-\\%d-\\%Y).log >/home/dgp/.\33[01;31m\33[Kclam\33[m\33[Ktk/db/fresh\33[01;31m\33[Kclam\33[m\33[K_cron.log 2>&1 ; /usr/local/bin/\33[01;31m\33[Kclam\33[m\33[Kdscan --reload --log=\"$HOME/.\33[01;31m\33[Kclam\33[m\33[Ktk/history/$(/bin/date +\\%b-\\%d-\\%Y).log\" >>.\33[01;31m\33[Kclam\33[m\33[Ktk/history/\33[01;31m\33[Kclam\33[m\33[Kscan.log 2>&1 ; if [ `fuser .\33[01;31m\33[Kclam\33[m\33[Ktk/history/\33[01;31m\33[Kclam\33[m\33[Kscan.log 2>/dev/null` = \"\" ]; then echo Still running >>.\33[01;31m\33[Kclam\33[m\33[Ktk/history/\33[01;31m\33[Kclam\33[m\33[Kscan.log ; else /usr/local/bin/\33[01;31m\33[Kclam\33[m\33[Kdscan --quiet --multiscan --fdpass --log=\"$HOME/.\33[01;31m\33[Kclam\33[m\33[Ktk/history/$(/bin/date +\\%b-\\%d-\\%Y).log\" / >>.\33[01;31m\33[Kclam\33[m\33[Ktk/history/\33[01;31m\33[Kclam\33[m\33[Kscan.log 2>&1 ; fi # fresh\33[01;31m\33[Kclam\33[m\33[K update and \33[01;31m\33[Kclam\33[m\33[K-scan\n", 965) = 965 ======================== dgp@dgp-p6803w:~ $ stty -a speed 38400 baud; rows 25; columns 80; line = 0; intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>; eol2 = <undef>; swtch = <undef>; start = ^Q; stop = ^S; susp = ^Z; rprnt = ^R; werase = ^W; lnext = ^V; discard = ^O; min = 1; time = 0; -parenb -parodd -cmspar cs8 -hupcl -cstopb cread -clocal -crtscts -ignbrk -brkint -ignpar -parmrk -inpck -istrip -inlcr -igncr icrnl ixon -ixoff -iuclc -ixany -imaxbel iutf8 opost -olcuc -ocrnl onlcr -onocr -onlret -ofill -ofdel nl0 cr0 tab0 bs0 vt0 ff0 isig icanon iexten echo echoe echok -echonl -noflsh -xcase -tostop -echoprt echoctl echoke -flusho -extproc dgp@dgp-p6803w:~ $ echo $TERM xterm dgp@dgp-p6803w:~ $ pse xterm UID PID PPID C STIME TTY TIME CMD dgp 3841 1862 0 12:38 ? 00:00:03 xterm -T x3831 -n x3831 -geometry 80x25 -fn 12x24 -sb -vb -cn -sl 9999 -ls dgp 3877 1862 0 12:38 ? 00:00:01 xterm -T x3867 -n x3867 -geometry 80x25 -fn 12x24 -sb -vb -cn -sl 9999 -ls dgp 3913 1862 0 12:38 ? 00:00:01 xterm -T x3903 -n x3903 -geometry 80x25 -fn 12x24 -sb -vb -cn -sl 9999 -ls dgp 3949 1862 0 12:38 ? 00:00:01 xterm -T x3939 -n x3939 -geometry 80x25 -fn 12x24 -sb -vb -cn -sl 9999 -ls dgp@dgp-p6803w:~ $ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1983276/+subscriptions -- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to xterm in Ubuntu. https://bugs.launchpad.net/bugs/1983276 Title: xterm processing grep color loses char at end of line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xterm/+bug/1983276/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp
