Marc Weber 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.
Well, you already understand the essential: Use tabs as much as possible, use spaces to put it in the right place. The default options for 'cindent' and the modeline in the file are obviously the way to go. There are plenty of examples, most people pick it up easily. -- Latest survey shows that 3 out of 4 people make up 75% of the world's population. /// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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.
