RE: [PEAR-DEV] VIM config in PEAR files?
| From: | Richard Heyes | Date: | Mon, 15 Apr 2002 10:08:33 +0000 |
| Subject: | RE: [PEAR-DEV] VIM config in PEAR files? | ||
| References: | 1 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-5514@lists.php.net to get a copy of this message | ||
> > 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.
Well you chose your editor, so that's really your problem.
> > 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.
Again, your editor, your problem. Presumably though Vim has sufficiently
caught up with Windows based editors to have a search and replace feature?
> > 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.
I would hazard a guess that the vast majority of php developers use some
sort of *nix, and thus vim, so it makes sense to use the comments. I doubt
the distribution of vim vs other editors is the same with PEAR.
> > 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 ;)
All Linux editors suck.
--
Richard "Muahahahha" Heyes
"If you have any trouble sounding condescending,
find a Unix user to show you how it's done." - Scott Adams