On 7/30/22 17:42, David G. Pickett wrote:
Any clues on how I got an xterm to mess up?
Presumably by sending that sequence of escape characters to xterm. You
should be able to reproduce the problem by using grep --color=always and
sending the output to a file F, and then by typing 'cat F'.
A
00:00:01 xterm -T x3903 -n x3903 -geometry 80x25 -fn 12x24 -sb -vb -cn -sl
-lsdgp 3949 1862 0 12:38 ? 00:00:01 xterm -T x3939 -n x3939
-geometry 80x25 -fn 12x24 -sb -vb -cn -sl -lsdgp@dgp-p6803w:~$
-----Original Message-
From: Paul Eggert
To: David G. Picke
I'm not seeing the problem on Ubuntu 22.04 LTS, using grep 3.7 and GNOME
Terminal 3.44.0 using VTE 0.68.0 +BIDI +GNUTLS +ICU +SYSTEMD. The output
isn't even colored unless I pass something like '--color=always' to
'grep', which leads me to wonder whether you're using an alias for
'grep' instead
On 30 Jul 2022, at 17:57, David G. Pickett via Bug reports for GNU grep
wrote:
>
> I was stunned to see the grep command remove bytes:
>
> $ crontab -l|grep clam30 23 * * * /usr/bin/freshclam
> --datadir=/home/dgp/.clamtk/db
> --log=/home/dgp/.clamtk/db/freshclam.$(/bin/date +\%b-\%d-\%Y).log
I was stunned to see the grep command remove bytes:
$ crontab -l|grep clam30 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 --config-file=/etc/c
