Hi
I'm having a bit of a wierd problem with text files potentially containing
corruption in the form of control characters. I fairly sure the problem
may not be the text file but the tool I'm using to view the file, which is
*more*.
The files are normally about 1900 lines long and have a ^^M on the end of
the line. If I use a cat -v the file looks fine. I thought that cat -v
would show up all control characters, but when I *more* the file these
other characters come up at what looks like the same place (say 25% through
and then later too). I've looked at many of these files through *more* and
they all have the same problem. I'm wondering whether *more* has some sort
of shared memory problem or is picking up something OS level and giving
these characters.
Another thing is that the corruption I can see with more moves up if I add
text to the begining of a file. All leading towards more craping out. We
have also used od -c successfully on the file. The weird thing is I can
*more* large file without the ^^M appended to each file successfully, so I
guess it must be some combination of factors causing the *mor*e problem
So I guess what I really want to find out is if there is a known problem
with *more*?
Should cat -v see all unprintable character? (I'm fairly sure od -c
should)
Can anyone throw any light on what's going on?
Thanks in advance,
Jase.
Received on Fri Nov 21 1997 - 22:03:28 NZDT