Re: [ jEdit-devel ] svn:eol-style = native (LF vs CRLF)

[Dale A. <da...@gr...>]

Tell me a bit more about this.  I've ran into problems with files that 
are generated by javacc.  I check the generated files into svn so that 
others can compile from source, but don't have to install javacc first.  
The problem with the generated files is that they always use the 
platform specific line enders.  So if I run javacc on Windows, I get 
crlf, and when I checkin the file and the previous commit used lf only, 
svn complains and won't let me.  Then I need to open the file and change 
the line enders (pretty easy, but a still a minor annoyance).  I've 
thought about writing a macro to automatically do the conversion, but 
haven't got around to it, or something added to the TextTools or 
WhiteSpace plugins (who has time?) or since the files I have trouble 
with are the javacc generated files, maybe change javacc itself.  Does 
what you're talking about just enforce the line ender policy, or will it 
help actually change files to the right line enders on the fly?  
Personally, I like to set the line separators to unix style, regardless 
of the platform.

Thanks,

Dale


Kazutoshi Satoda wrote:
> Alan Ezust wrote:
>  > I did some googling to better understand it and came across this thread:
>  > http://www.mail-archive.com/har...@in.../msg13473.html
>  >
>  > Is it necessary to impose such a policy among all committers of the
>  > jedit project?
>
> Yes. Manual settings on each committer's machine is one of the best
> practices. Unfortunately, it can't be per project. It is per machine.
> So we can't enforce the settings.
>
>  > If so, should we point them to the apache svn config
>  > file, since it is probably going to be similar for committers of
>  > project jedit?
>
> It looks quite well defined one. But since it is a setting per machine,
> having a reduced set for project jedit in the own repository might be
> preferable.
>
>
> More aggressive approach is, setting pre-commit hook script which
> checks the property of adding files and rejects a commit which doesn't
> match a policy. In this way, the policy is applied per repository.
>
> I found that SourceForge.net have fine supports of hook scripts. They
> provide some common hooks, and check-mime-type.pl is a similar
> function.
>    https://sourceforge.net/docman/display_doc.php?docid=31070&group_id=1#scripts
> So submitting a new Feature Request might be appropriate. One assumed
> issue is that checking eol-style requires a configuration like the
> auto-prop setting.
>
> --
> k_satoda
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
>