12 Oct, 2007, David Haley wrote in the 2nd comment:
I'm not sure, since I haven't used it for ages, however, I suspect that your text file might have just one or two bytes of binary (any non-text, really) that confuses whatever heuristic Crimson Editor uses. I'd suggest opening the file in a hex editor or something and seeing what exactly is in the file.
12 Oct, 2007, Zeno wrote in the 3rd comment:
The files are thousands of lines long. Do you mean I have to manually read the file?
12 Oct, 2007, Conner wrote in the 4th comment:
Well, unless you can think of another way.. :shrug:
12 Oct, 2007, David Haley wrote in the 5th comment:
I imagine that its heuristic only looks at the first few lines. I'd look at just those, at least, and see if there's anything unusual there.
15 Oct, 2007, Zeno wrote in the 6th comment:
Nope, the first fine lines is just normal text (same as what a normal text editor shows).
15 Oct, 2007, David Haley wrote in the 7th comment:
I'm kind of stumped then, I would have assumed that it used the first x bytes of the file to guess if it was text or binary. Sorry. :thinking:
Random Picks
I'm doing a "search in files" using it. But it keeps on skipping various .txt files because it says it is a binary file. Any idea how to fix this? I can view the .txt file just fine, I dunno why it's considered binary.