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

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

Hmm... It looks like my last "experiment" might have been flawed...
Since it was very fishy that a file was being exported with CRLF EOLs
even on a unix machine, I tried again:

dos> date > dosfile3
dos> unix2dos dosfile3
dos> cvs add dosfile3

I checked to see if the file had the '-kb' sticky tag. It didnt.

unix> cvs update
unix> vim dosfile3

And now dosfile3 doesn't have the '^M' characters and its also ff=unix.

So I don't know what went wrong last time...

In any case, setting -kb for the files might actually be a bad idea
because in some situations, a cvs client might create dos style files on
a unix clients... Bad Idea!

So what I propose is the following:

Unsetting the -kb flag from all our files.

This will have the side-effect that cvs clients on windows machines will
create dos style EOLs. Therefore its not possible to create packages via
a DOS machine... But as I mentioned previously, this shouldn't be
a problem because I create releases from my linux account on sf.net.
Also, it will enable using keyword substitution...

Also, as far as verifying that the files are all in unix format at
release time, Ulrich Spoerlin suggested I use:

file `find . -print` | grep CRLF | sed s/:.*// | xargs dos2unix

I'll add this to our makefile just to make doubly sure...

Srinath

PS: The tip about 'ffs' was very helpful! Turns out there that the
system vimrc on sf.net sets lots of very nondefault values, one of those
being 'ffs=unix' with the comment "I want to see those ^M characters
when I am editing dos files"... Go figure.