On Sat, Jun 01, 2013 at 11:45:44PM -0700, Yegappan Lakshmanan wrote: > Hi,
> On Sat, Jun 1, 2013 at 10:58 PM, tooth pik <[email protected]> wrote: > > On Sat, Jun 01, 2013 at 10:49:37PM -0700, Ben Fritz wrote: > >> On Sunday, June 2, 2013 12:24:11 AM UTC-5, MarcWeber wrote: > >> > ZyX told me that I should try to write the way the source code looks. > >> > > >> > Now I find that files mix tab with spaces etc. > >> > > >> > The src/README.txt talks about many things, but not about how to > >> > configure Vim to write Vim's .c code. > >> > > >> > Would you mind adding a section or a reference to a .vim file describing > >> > how to format Vim's C code properly? > >> > > >> > Eg os_unix.c contains a line 1439 like this: > >> > return TRUE; /* exit! */ > >> > > >> > 4 tabs, one space, then "return TRUE" > >> > > >> > If you want contributors to do the right thing document it briefly. > > > >> I think it's just: > > > >> :set sts=4 sw=4 ts=8 > > > >> It throws me, too. I don't like it. > > > > what about expandtab? I've seen spaces and tabs and remain > > confused... > > > > isn't the most bulletproof rule to always expandtab so no matter what > > the tab setting the code appears the same? > > > These settings are used so that as few characters (a mix of tabs and spaces) > as possible are used to indent the code. you gotta be kidding -- in the age of terrabyte hard drives we're tryin to save space!?!?!? -- _|_ _ __|_|_ ._ o| |_(_)(_)|_| ||_)||< | -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
