Bill McCarthy wrote:
> >> When I checkout vim7 with svn under WinXP Pro, my text files
> >> are all coming out as UNIX files (using LF instead of
> >> CR/LF).
> >>
> >> The svn program is designed to handle proper EOL for an
> >> operating system when a property called svn:eol-stype is set
> >> to "native".
> >>
> >> Am I supposed to do anything special to cause svn to give my
> >> text files to be stored as standard CR/LF files?
> >
> > Why do you want CR-LF files? A single LF should work just fine.
>
> The svn docs explain this quite well. Some programs fail to
> properly deal with LF only. A good example is Microsoft
> notepad.exe.
In the context of Vim I don't think we should worry about notepad users.
> > Automatic LF to CR-LF translation always causes trouble somewhere.
>
> I have never had a problem with CVS doing this. I believe
> the "trick" is to only mark 'native' those files which are
> indeed text files.
Right. So what if files aren't properly marked as text or binary? And
there always is a mistake somewhere (I recall there was an icon file
that was broken for a year before someone discovered it should be marked
binary).
I've seen too many files with mixed line endings, this can be a real
mess. Especially Unix files that were edited in Visual studio.
Also remember that files on a USB stick will never adjust to the
computer you plug it into. Systems must be able to deal with both LF
and CR-LF.
There is only one solution eventually: Drop those CR-LF line separators.
It just takes a bit of time before all MS-Windows programs can deal with
them.
--
hundred-and-one symptoms of being an internet addict:
96. On Super Bowl Sunday, you followed the score by going to the
Yahoo main page instead of turning on the TV.
/// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ download, build and distribute -- http://www.A-A-P.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
