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

[Benji F. <be...@me...>]

Srinath Avadhanula wrote:
> Hello,
> 
> It looks like we need to rethink how to set the keyword expanion mode of
> our files... What would be ideal for us is if CVS is able to inhibit
> CRLF conversions while also permitting expansion of stuff such as
> $Header$. Unfortunately, it looks like CVS is a bit confused about line
> endings and keyword substitutions. The only way of inhibiting EOL conversions
> is to tell CVS that the file is binary, which unfortunately throws away
> keyword subsitution.
> 
> The following thread in google groups sounded promising, but my cvs
> client doesn't seem to support the CVS_MODE variable which is proposed
> there. (The online manual at cvshome.org also doesn't mention CVS_MODE).
> It also mentions that jCVS is able to do what we want, but I do not have
> time right now to try it.
> 
> http://groups.google.com/groups?hl=en&lr=&ie=UTF-8&threadm=fa.ion3edv.6g8l9e%40ifi.uio.no&rnum=1&prev=/groups%3Fq%3Dline%2Bconversion%2Bgroup:fa.info-cvs%26hl%3Den%26lr%3D%26ie%3DUTF-8%26selm%3Dfa.ion3edv.6g8l9e%2540ifi.uio.no%26rnum%3D1
> 
> The only way to have keyword expansion is therefore to remove the -kb
> flag from files. So the question is:
> 
> Are there platforms for which the cvs client performs a CRLF conversion
> which vim doesn't like? Is one of us developers on such a platform? If
> so, should we bother unsetting the -kb flag to allow keyword
> subsitution? Or should we just forget about keyword substitution?

      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?".

      I have always thought that -kb was a bit of an abuse.  OTOH, I am 
not sure that keyword substitution gives us anything very useful.

> Note, that since I make releases via my sourceforge shell account, the
> .zip and .tar.gz packages always have UNIX style EOLs in the files,
> which should be fine with vim on any platform...

      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.

					--Benji