On Tue, Dec 19, 2006 at 01:08:14PM -0800, Allison Randal wrote: > Nicholas Clark wrote: > >On Tue, Dec 19, 2006 at 10:05:46AM -0800, Allison Randal wrote: > > > >>to every source file, and a maintenance burden. Both vim and emacs allow > >>top-level settings of these preferences, which is a more appropriate > >>place for them. > > > >This assumes that all the projects you use the editor for have the same > >standard. (assuming that you're meaning to set the defaults for C and Perl > >formatting modes, rather than to use custom parrot-mode variants) > > All it does is turn on cperl mode for emacs, and set tabs to 4 spaces > for vim and emacs. Not likely to significantly interfere with any > repository you work on. (I actually gave up on the tab key in vim years
To seek clarification - having those as global settings for cperl isn't likely to be an issue? Or having them in editor blocks? > I do like Chris's parrot-mode solution better than including the literal > option commands in every file. It at least reduces the clutter and > maintenance headaches. This seems good. emacs (or at least one version) quietly warns that it's ignoring the unknown mode, then carries on as if the mode line wasn't there. Nicholas Clark
