C. Chad Wallace on 22/11/05 02:38, wrote:
Stephen Rueger wrote:Adam Hardy <adam.ant@cyberspaceroad.com> 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...
That's right. the file .bash_history command reported it as "data", although emacs wasn't phased by it. Grep didn't like it though. Unfortunately since I zapped it, I can't generate the error anymore. I guess I could restore the file from a backup. Would it be worth it?
Adam