On Thu, Apr 07, 2011 at 07:51:53PM +0200, Louis Hoefler wrote:
> I never had problems with LF line endings in my batch files/source files/
> whatever
> I am on windows 7 with vs2010.
> 
> The only thing whitch troubles me is the linux shell interpreter who can not
> live with CR-LF line endings and renames dirs to dir^M.
> 
> For god sake let windows out of this, becouse it (currently) works better with
> different line endings than linux (currently) does. As you see.
> I'm sure it was different in the 80's and 90's.

Actually, we maintain old code which are in vs6, and it's true, it
really doesn't like lf line ending. 

I don't know about vs2010, but vs2005 (like vs6) had problem with
project files being mixed between lf and cr-lf, and it was silently
adding cr-lf inside a lf file resulting in a mixed cr-lf file which is
pretty dumb (instead of detecting line ending and adding lf when it's an
unix file)

> 
> Back to the topic:
> Converting files between different OS is an unnecessary feature to me.
> You can convert more accurate if you write your own scripts to do that.
> That's like deleting unneeded files out of directories.
> I wrote a simple tcl script and qt programm to do that:
> http://sourceforge.net/projects/dircln/files/
> 
> 1. cleandir
> 2. dos2unix
> 3. fossil add *
> 4. fossil commit
> 5. dos2unix
> 
> If someone does not want to use the 5 commands all the time, wrap it into a
> shell script.
It's only that when the scm take care of it, it's transparent and you
don't have to convert back and forth when you diff files and when you
want to check status of you tree (which files are modified) you get all
of them. 

> 
> PS:
> Converting files to different line endings is already available on most
> systems. Even vs2010 can do it, and it's plugin and macro system is (almost)
> one of the best.
> 

For myself, working on linux (or bsd), I don't get stuck when source
code get mixed or cr-lf line ending, I see those blue ^M in vim and
I get rid of them easily, it's just an annoyance. 

I've just ask about this feature because we have it with CVS for long
time and we never had problem with that, it simplify our workflow
actually. 

But I can leave without it, at least with this warning message recently
added, it will avoid those mixed line ending file that might be commited
by accident.

Regards

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

Reply via email to