On Mon, Sep 20, 2010 at 10:46 PM, Gustavo Sverzut Barbieri
> On Mon, Sep 20, 2010 at 10:21 PM, Brett Nash <nash@...> wrote:
>> No, that's just backwards.
>> I contribute to multiple projects, I don't want to have to set up
>> multiple vim rcs just to edit e files. And I'm sure as hell not going
>> to convert multiple groups coding standards (if so, E loses BTW).
>> _IF_ moodelines were significantly different between different versions
>> of vim, it may be an issue, but really it's not. Modelines means I can
>> just open up a file and edit without futzing around working out the
>> appropriate coding standard.
>> Especially since maintaining modelines to follow the one true standard
>> is really easy: A perl oneliner can update all the modelines in a
>> porject _really_ easily.
>> Keeping a central 'this is the correct modeline' would be nice.
> I disagree fully. If you are a random contributor to projects, it's
> easy to figure out the correct style code just by looking around and
> copying it. Likely there is more than tabs-and-spaces-and-braces
> problem to the style, things like naming schemas and others you have
> to match... in any case you'll either be corrected by upstream, or
> they will be permissive and accept it as is.
> HOWEVER, for long time contributions to code (most of us), you MUST
> have a proper setup for your project. You must setup some way to say
> "for this you use that". In our case we often checkout the whole SVN,
> so I assign ~/Development/svn/e to our code style.
ah! And I forgot the main issue to back this answer: there is no "EFL
editor", thus you can't help everybody. I use emacs myself and don't
give a shit about vim. People that use vim don't give a shit to emacs.
Raster himself uses a weird editor nobody else uses. Then Leandro uses
yet-another, then some guy here uses kate... you got it: you'll not
"fix" the said problem by having these things in.
Gustavo Sverzut Barbieri
http://profusion.mobi embedded systems
Mobile: +55 (19) 9225-2202