bug#56843: closed (grep mangling lines)

[GNU bug Tracking System]

Your message dated Sat, 30 Jul 2022 21:50:06 -0700
with message-id <19578b8a-16b7-4957-596a-25fcae9273b8@cs.ucla.edu>
and subject line Re: bug#56843: grep mangling lines
has caused the debbugs.gnu.org bug report #56843,
regarding grep mangling lines
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
56843: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56843
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

--- Begin Message --- Subject: grep mangling lines Date: Sat, 30 Jul 2022 15:57:39 +0000 (UTC)

I was stunned to see the grep command remove bytes:

$ crontab -l|grep clam

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 --config-file=/etc/clamav/clamd.conf --reload --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" >>.clamtk/history/clamscan.log 2>&1 ; /usr/local/bin/clamdscan --config-file=/etc/clamav/clad.conf --quiet --multiscan --fdpass --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" $HOME >>.clamtk/history/clamscan.log 2>&1 # freshclam update andclam-scan

from this line:

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/freshclam_cron.log 2>&1 ; /usr/local/bin/clamdscan --config-file=/etc/clamav/clamd.conf --reload --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" >>.clamtk/history/clamscan.log 2>&1 ; /usr/local/bin/clamdscan --config-file=/etc/clamav/clamd.conf --quiet --multiscan --fdpass --log="$HOME/.clamtk/history/$(/bin/date +\%b-\%d-\%Y).log" $HOME >>.clamtk/history/clamscan.log 2>&1 # freshclam update and clam-scan

On my 80x25 xterm, the missing byte should have been at the end of the line, and is highlighted in red.  Highlighting is ok but accurate data is nicer?

--- End Message ---

> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#56843: grep mangling lines
>
>
>
>
> Date: 
>
> Sat, 30 Jul 2022 21:50:06 -0700
>
>
>
>
> User-agent: 
>
> Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
>
>
>
>
> 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'.
>
> As this is not a grep bug, I'll close the grep bug report.
>
>
> --- End Message ---