Re: VIM config in PEAR files?

On Mon, Apr 15, 2002 at 12:28:51PM -0400, Jon Parise wrote: > On Mon, Apr 15, 2002 at 12:12:57PM +0200, Lukas Smith wrote: > > > Then that should not be the case. > > Just check freshmeat.org to get a glimpse of the amount of editors out > > there. This is just unncessary bloat or does PEAr want to adopt an > > editor is the one and only? > > The bloat occurs when a developer (accidentally) commits code that > does not conform to the coding standards and then follows up that > first commit with a style or whitespace commit. That why we should use tabs and not spaces. It doesn't matter how many places a editor uses for a tab. A tab is a spacial character (ASCII 9). And what if a developer is near-sided and he want to use 12 places in stead of 4 for indenting. With tabs that is possible (Every editor i know (*nix, windows, max, amiga, etc) has an option to set the tab width). I don't care that diff is displaying tabs as 8 places and an editor as 4. I writing code, i'm not a publisher.. > > Oh another solution is to work with all the editor writers to establish > > a standard that is used by enough editors to make it worthwhile > > including. > > That's a totally unreasonable suggestion, and everyone knows it. It > doesn't even rate highly on the sarcasm scale. Please don't bloat my > mailbox with such unnecessary comments. I agree with that. The PEAR indenting standard is 4 spaces. (which should be 4 places..) And as long a editor is displaying it as 4 places there's nothing to worry. But the fact that VIM has an option that convert tabs into spaces isn't my problem. Are are you VIM developers actually typing 4 spaces?? Please just leave it as a tab. Dave Mertens