Re: [SM-CVS] CVS: smdoc/templates ... very long subject ...

[Marc G. K. <ma...@sq...>]

> Thijs Kinkhorst said:
>> On Thu, August 12, 2004 3:51, Erin Schnabel said:
>>=20
>>> The correct way to handle vim syntax is not to litter all of your
>>> files with vim tags (I don't like seeing this in SM proper, either.. =
)
>>>=20
>>=20
>> Disagree. Adding such a tag also works for people that have just
>> checked out the code and requires no extra action on their part.
>> Especially for the expandtabs option, our code keeps getting formattin=
g
>> problems, and making sure that the settings are by default right for
>> committers reduces the chance that they 'screw up' our code.
>>=20
>> Why require extra action on the part of the user to make it work, whil=
e
>>  we can easily make it so that it works right "out of the box"? I see
>> no objection to that at all.
>>=20
>>=20
>> Thijs
>=20
> Not everyone uses Vim, Thijs. So it *still* won't cover all cases. Ther=
e
> is a document buried in the SM wiki called "Coding Style" - this should
> perhaps be updated (and a copy placed on nuts.netdork.net) to include t=
he
> little nits for making vim treat templates like php.
>=20
> Again, littering our codebase with vim tags is not appropriate. We may
> have a few that like emacs, and I know we have some that do editing on
> weekends. If you're going to be a developer, it's par for the course to
> know how to tell your editor what is up.. And really, I haven't seen co=
de
> being messed up lately - Marc figured out how to make his editor behave=
..
> ;)  *hahaha*
>=20

Hehe, yes, now I have an editor (KDevelop) where I can actually see the t=
abs ;). No vim for me.

Marc.