Please, do not oversimplify the situation. Just one example:
1- A TCL file is checked in on windows
2- It is checked out on unix and line ending is "\r\n"
3- Many TCL files start with:
#!/bin/sh
# the next line restarts using wish \
exec wish "$0" "$@"
4- chmod +x $file
5- This file is NOT going to execute on Unix
Second example:
1- I create a nice README or License file for my application in unix
2- I checkout in Windows
3- README files are open by the user (not by my that I use a wonderful
convert-all editor). In Windows, they typically open with Notepad.
4- The file is viewed as with one very long line
I am sure that I can find much more examples.
2009/10/21 Joshua Paine <[email protected]>:
> On Wed, 2009-10-21 at 16:36 +0200, Ramon Ribó wrote:
>> In any case, what is your proposal for using fossil to manage a program
>> both in unix and windows?
>
> Use a competent text editor? Essentially every text editor meant for
> programmers can trivially convert line endings or edit in either mode.
>
> I'm all-Linux now, but when I developed on Windows I just set my editor
> to use unix line endings.
>
> --
> Joshua Paine
> LetterBlock: Web applications built with joy
> http://letterblock.com/
> 301-576-1920
>
> _______________________________________________
> fossil-users mailing list
> [email protected]
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
