Re: [fossil-users] cannot compute difference between binary files

I had a similar problem and realized it was because I had a single character that was considered 'binary' by fossil's diff'ing algorithm and got the behavior you're seeing. My local copy of fossil has LENGTH_MASK_SZ set to 24 and the following patch (previously sent to the list) to alleviate the

Re: [fossil-users] Question about binary file detection

You're right that would be a cleaner solution. The truth is, the offending line in my script was commented out. So in this case I didn't even need a better solution. My question still stands though, should a single 'binary' character cause fossil to consider a file binary, and thus make it

[fossil-users] Question about binary file detection

I had a seemingly normal python file checked in and when I went to view the artifact, fossil claimed it was binary. I tracked it down to a line like this in my source: sys.stdout.write('^H') Where the ^H is 0x8, the backspace character. It seems my otherwise text looking file was marked

Re: [fossil-users] Question about binary file detection

Now the second attempt at attaching the patch. Bill On Thu, May 19, 2011 at 06:45:52PM -0700, Bill Thiede wrote: I had a seemingly normal python file checked in and when I went to view the artifact, fossil claimed it was binary. I tracked it down to a line like this in my source