Groups > alt.os.linux.slackware > #26024

Re: grep in non linux EOL?

From	Rich <rich@example.invalid>
Newsgroups	alt.os.linux.slackware, comp.os.linux.misc, alt.os.linux.debian
Subject	Re: grep in non linux EOL?
Date	2015-12-27 05:19 +0000
Organization	My Linux Box
Message-ID	<n5nsdn$630$1@dont-email.me> (permalink)
References	<n5n68j$ft6$1@dont-email.me>

Cross-posted to 3 groups.

Show all headers | View raw

In alt.os.linux.slackware no.top.post@gmail.com wrote:
> It's OK if you want to donate your much-better-version. But what I
> really need to know is the REASONING BEHIND why my version fails.

Because you have 'mixed' three different text file line endings
together.  Don't do that.  Convert the 'dos' and 'classic mac' line
ending files to unix style before applying grep to them.

> With dir-trees having mixed-format text-files: 3 types:
> *nix, DOS, EOL=x0d, I need to find files containing a string: $1
>   Testing LEOfind:-
> #!/bin/bash
> find  /sa5/Legal/CIPC  -exec grep  "$1" {} \; 2>/dev/null | fold | grep $1
>     with ./LEOfind Gates , gives me also some lines which do NOT contain
>     "Gates".
> Surely `<any command> | grep Gates`
>  must consist of lines, each containing "Gates"

Classic Mac files end lines with 0x0d (carriage return).  Carriage
return on Linux is an "overprint current line" signal for the terminal.

So, if one of your Mac files has this:

line # 1 Gates\rline # 2 something \rline # 3 someting else\r\n

where \r is the Mac carriage return, a Classic Mac would see three
lines, but grep will see all of the above as one single line (because
grep only ends 'lines' when it finds a \n character).  And grep will
print all of the above to the terminal (because "Gates" does occur
within the 'line' as grep understands it.  But, after printing the
above to the terminal, you will only see:

  line # 3 something else

Because each of #1 and #2 was overlaid by the Mac 'line' that came
after it.

Thread

grep in non linux EOL? no.top.post@gmail.com - 2015-12-26 23:01 +0000
  Re: grep in non linux EOL? Rich <rich@example.invalid> - 2015-12-27 05:19 +0000
    Re: grep in non linux EOL? no.top.post@gmail.com - 2015-12-29 20:05 +0000
    Re: grep in non linux EOL? no.top.post@gmail.com - 2015-12-30 02:05 +0000
  Re:grep in non linux EOL? Doug Laidlaw <laidlaws@hotkey.net.au> - 2015-12-28 20:31 +1100
  Re:grep in non linux EOL? Doug Laidlaw <laidlaws@hotkey.net.au> - 2015-12-28 20:47 +1100
    Re: grep in non linux EOL? The Natural Philosopher <tnp@invalid.invalid> - 2015-12-28 10:18 +0000
      Re: grep in non linux EOL? floyd@apaflo.com (Floyd L. Davidson) - 2015-12-28 04:05 -0900

csiph-web