Re: VIM config in PEAR files?
| From: | Markus Fischer | Date: | Mon, 15 Apr 2002 08:16:21 +0000 |
| Subject: | Re: VIM config in PEAR files? | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-5502@lists.php.net to get a copy of this message | ||
On Mon, Apr 15, 2002 at 10:52:40AM +0200, Dave Mertens wrote :
> On Sun, Apr 14, 2002 at 11:11:48PM +0200, Markus Fischer wrote:
> > On Sun, Apr 14, 2002 at 10:11:24PM +0100, Richard Heyes wrote :
> > > > On Sun, Apr 14, 2002 at 10:04:43PM +0200, Tomas V.V.Cox wrote :
> > > > > Markus Fischer wrote:
> > > > > >
> > > > > > I hardly see any vim config comments in the PEAR source files
> > > > > > (so that tabs are properly expanded to spaces, etc).
> > > > > >
> > > > > > Any objection if I add them where needed?
> > > > > >
> > > > >
> > > > > I don't like too much the idea to "dirty" the files with
> > > > > specific editor
> > > > > stuff.
> > > >
> > > > Why?
> > >
> > > A better question might be "Why vim?".
> >
> > Because *I* use vim and intend to place the proper definition
> > into it so *everyone* using vim will automatically have the
> > right mode (no tabs, spaces) when editing the files and the
> > chance of commited something with fu@#^ up whitespaces is
> > low.
>
> And VIM doesn't have a config file where you can set those options for a file type??
It has. But how should I distinguish if I edit my personal
PHP file which has a different coding standard or if it's a
PEAR file? There is no obvious mark which tells that.
> I think that i doesn't matter if you're writing PHP PEAR code or just
> 'normal' PHP code.
I write my code with TAB's instead of Spaces. PEAR standard
is spaces. So, actually, it does matter.
> Or do you VIM users use for each file different options?
As you see my personal preference is different from the PEAR
coding standard. This, however, does not only apply to PEAR
but code in gerneal. See the C source code of PHP. Every
programmer has his own, personal, preference. Yet the goal is
to have a code which does not switch between coding styles.
This is achieved by putting special commands for the
different editors in comments or whereever they fit best.
> Or maybe you should use a editor (joe,pico,mc editor) that don't need a file specific
> config line.
Well, they all suck big time and are not adjustable to my
personal preference. I've seen them all in my life ;)
- Markus
--
Please always Cc to me when replying to me on the lists.
GnuPG Key: http://guru.josefine.at/~mfischer/C2272BD0.asc
"Mind if I MFH ?" "What QA did you do on it?" "the usual?" "ah...
none :)"