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 unviewable through the ui.
Bill
On Fri, May 20, 2011 at 01:49:59PM +0400, teh...@ya.ru 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:
> >
> > sys.stdout.write('^H')
> >
> > Where the ^H is 0x8, the backspace character. It seems my otherwise text
> > looking file was marked binary by mimetype_from_content() in src/doc.c
>
> Any reason of having (binary) 0x08 character when there is \b?
> _______________________________________________
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
