control M characters

[Rinky]

Hi,
I wanna check if a file contains control M [^M]
characters in it.
Not a perl script, but a shell script solution.
Can I check for it

[Dennis Handly]

If you want to just convert them, you can use dos2ux(1).

Otherwise you can use grep but you'll have problems getting a control M into the shell.

I was able to use control V, then control M in vi to get:
$ fgrep -q ^M file

[Yogeeraj_1]

hi

try:
find . -type f |xargs grep -l ^M

Where the ^M character should be typed as:
ctrl+v ctrl+m

hope this helps!

kind regards
yogeeraj

[Rinky]

fgrep -q ^M file
dint work..
I have attached the file.
You can test this file

[Dennis Handly]

>fgrep -q ^M file
dint work.

Works fine for me using a real shell. As I said, you have to create a script with control M. You can't enter it directly to the shell.

[Dennis Handly]

Here is my script.

[James R. Ferguson]

Hi Rinky:

What's (?) so hard with:

# perl -ne 'print if /\015/' file

THe \015 is the octal code for a Carriage-Return which is graphically seens as ^M. The Perl snippet reads every line of a 'file' passed printing any line that has a carriage-return in it.

Regards!

...JRF...

[OldSchool]

...or you can stick the ^M in a "pattern file" and use it. for example, file "P1" contains the Ctrl-M, then you can do:

grep -f P1

or for all Control characters, try

grep [:ctrl:]

[Sandman!]

Simplest would be to grep for the Ctrl-M character which is inserted into the cmd line by holding down the "Ctrl", "V" and "M" keys simultaneously on your keyboard i.e.

# grep -q ^M infile && echo "Ctrl M chars found" || echo "No Ctrl M chars found"

[OldSchool]

FYI:

Sandman, your solution occurred to me also, but when i tried it in ksh on 11.0, entering that key sequence generated a Ctrl-J on the command line. Suspect its an issue w/ "set -o vi" / .exrc / .kshrc, but didn't check further...just proceeded on in a different direction

[Sandman!]

You're right OldSchool I am unable to duplicate the command line I created under the sh-posix(1) shell. Hmmm...needs to be looked into.

[A. Clay Stephenson · Accepted solution]

Here's a sneaky way to do it leveraging echo.

If testing a shell variable then:

echo "${MYVAR}" | grep -q $(echo "\r\c")
STAT=${?}
if [[ ${STAT} -eq 0 ]]
then
echo "CR Found"
fi

If testing a file:

grep -q $(echo "\r\c") infile
STAT=${?}
if [[ ${STAT} -eq 0 ]]
then
echo "CR Found"
fi

[Dennis Handly]

>Sandman: I am unable to duplicate the command line I created

I kept saying that. But vi allows ^M.

[Arturo Galbiati]

Hi,
grep [\015] file

it's ok on my Hp-UX 11i

HTH,
Art

[Dennis Handly]

>Art: grep [\015] file

I almost took you at your word since I didn't check this. (I forgot what Ronnie said. ;-)
But now I did and this does not work in a real shell. What shell did you use?

A similar (but quoted) syntax works in tr(1): "[\015]"

[freddy_21]

try to run
#dos2ux test1 > test2

your ^M will be remove at file test2.


thanks
freddy

[Rinky]

grep -q $(echo "\r\c") infile
STAT=${?}
if [[ ${STAT} -eq 0 ]]
then
echo "CR Found"
fi

worked fine..
thanks..

[Rinky]

WOW!!
dos2ux test1 > test2
perfect command..
Thanks a lotttttt...

[Hein van den Heuvel]

Well duh!
Just like you were informed in the very first reply a week ago!

Cheers,
Hein.

[Dennis Handly]

>Hein: Just like you were informed in the very first reply a week ago!

Exactly.

Other than Clay's echo trick, OldSchool's file of CR and JRF's perl script, nothing was added since my first reply.
(And I only got 4 points. Though Rinky can add some more. ;-)

[Yogeeraj_1]

... and not to complain that the initial question was:

"I wanna check if a file contains control M [^M] characters in it."


Na Zdrave
(Bulgarian Cheers!)

yogeeraj