> On Sep 10, 2014, at 9:47 PM, Yury Gribov <tetra2...@gmail.com> wrote: > > Segher Boessenkool <segher <at> kernel.crashing.org> writes: >> I am saying it is very anti-social to make >> people's editor behave differently from what they are used to. >> ... >> The Emacs dir-locals file simply >> configures some settings for files with certain major modes in that > dir. >> For example, ours says that c-mode files should use GNU style. This > is >> quite harmless, and probably what most Emacs users want. > > Hm, so autoformatting in Emacs is good because that's what most users > want but autoformatting in Vim is bad because that's not what people are > used to?
I don't like auto formatting in any editor. Though I don't use emacs, I use vim. I think using auto formatting is cheating and not understanding why coding styles exists. And some folks already have to deal with two more formatting styles already: Linux kernel and gnu. So if you add auto formatting to one, some folks are going to get confused. Thanks, Andrew > >> First, you are encouraging >> the use of a plugin that is a gaping wide security hole. > > I don't think so. The comment mentions that user can either install a > (rather widespread btw) plugin or just call config from his .vimrc. > >> Secondly, this is a very poor imitation of the mechanism Vim has for > dealing >> with filetypes, namely, ftplugins. > > I'm ready to accept technical suggestions on how to do the thing > properly. So what exactly do you propose? > >> [Snipped some overly optimistic stuff about this all increasing the > quality >> of posted patches. Hint: the most frequently made formatting error is >> forgetting to put two spaces at the end of a sentence. > > Dunno, I was relying on personal experience. And searching for "two|2 > spaces" on http://gcc.gnu.org/ml/gcc-patches returns 2000 results > whereas "eight|8 spaces" only 700. > > -Y >
