On Fri, Sep 14, 2012 at 11:34 PM, Csaba Kos <[email protected]> wrote:

> I am a fossil novice myself, but I don't think there is such
> functionality built-in currently.
>

I was talking about tagging encoding as well as end of line handling, but
mainly I was giving myself an out in case I was speaking in favor of
something that already exists. :)


> My plan for the EOL conversion was to extend the syntax of the
> "crnl-glob" setting in the following way:
> *.txt:cr        < force CR
> *.txt:nl        < force NL
> *.txt:cr+nl   < force CR+NL
> *.txt:native  < convert to native format
> anything else: < allow CR+NL (current behaviour)
>
> But I agree that properties attached to files (similarly to
> subversion, perhaps) might be preferable for setting the encoding/line
> ending.
>

 That was my thought as well.

SDR
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to