Stephen Rueger wrote:
Adam Hardy <[EMAIL PROTECTED]> writes:
This used to work until recently when I found that the .bash_history had
been transformed into a data file, instead of the ASCII text that I was
used to.
How exactly did you find that out? If it's merely because grep says
something like "binary file .bash_history matches", chances are that
its rather stupid binary file detection screwed up again.
So, what does looking at it with a pager show? And what does file(1) report?
I just ran into this as well... file reported it as "data". Upon viewing it in less, I found that it had a whole bunch of nulls (^@ is null, right?) in it. I don't know where those would have come from...
--
C. Chad Wallace, B.Sc.
The Lodging Company
http://skihills.com/
OpenPGP Public Key ID: 0x262208A0
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
