Re: [Vim-latex-devel] CVS keyword expansion

[Srinath A. <sr...@fa...>]

On Thu, 9 Jan 2003, Benji Fisher wrote:

>
>       I think the only likely problem is if one of us uses DOS-style
> line endings, and they get uploaded to the CVS repository.  How do we
> test this?  Maybe we should each do a "cvs add" and then "cvs commit" on
> the test project, then someone using Linux (like me) can download the
> files and check with ":set ff?".

Okay. I just checked this. I did the following:

(On my dos machine):

dos > date > dosfile2
dos > unix2dos dosfile2
dos > cvs add dosfile2
dos > cvs ci -m 'was ff=dos when created' dosfile2

Then on my sourceforge account

nix > cvs update
nix > vim dosfile2

Guess what? I see the annoying ^M character at the EOL! But ff? gives me
'unix'. Setting ff=dos and saving doesn't help. However, doing
'dos2unix dosfile2' does help in removing the ^M character and ff is
also correctly identified as unix...

So well, I guess we are somewhat screwed if the file being commited is
in dos format. I am wondering why this didn't happen already...

But this problem is not really related to -kb at all... You'll notice
that I didn't use -kb anywhere... If I do

nix > cvs admin -kb dosfile2
nix > cvs update dosfile2

Even then, it doesn't help...

So whats the conclusion from all this? I really don't know...

>       Can you add something to the makefile that will check for and
> correct line endings?  It seems to be safe to run dos2unix on a file
> already in unix format; with the -k flag, it keeps the time stamp.

Yes... I'll do this. But what about files in which there are spurious ^M
characters?

Srinath