From: Jim Meyering Date: Wed, 12 Jan 2011 20:20:34 +0000 (+0100) Subject: doc: clean up HACKING guidelines X-Git-Tag: v8.10~72 X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=d95e3c8cebb98ea26a99a64c6bb1ad1024c38662;p=thirdparty%2Fcoreutils.git doc: clean up HACKING guidelines * HACKING: Remove mention of "indent-tabs-mode: nil", since we've remove all of those directives. No longer needed. Remove dated (pre-emacs-23) reference regarding WhiteSpace mode. --- diff --git a/HACKING b/HACKING index 2565d158f2..8933e9a744 100644 --- a/HACKING +++ b/HACKING @@ -468,10 +468,8 @@ versions of gcc and the linux kernel, and modern GNU tools. Ensure that your changes are indented properly. =============================================== Format the code the way GNU indent does. -In a file with the "indent-tabs-mode: nil" directive at the end, -running "indent --no-tabs" should induce no change. -With other files, there will be some existing differences. -Try not to add any more. +Filtering most source files through "indent --no-tabs" should +induce no change in indentation. Try not to add any more. Avoid trailing white space @@ -484,13 +482,11 @@ Do not add any more trailing blanks anywhere. While "make syntax-check" will alert you if you slip up, it's better to nip any problem in the bud, as you're typing. A good way to help you adapt to this rule is to configure your editor to highlight any offending characters in the -files you edit. If you use Emacs, customize its font-lock mode (FIXME: -provide more detail) or try one of its whitespace packages. This appears -to be the one that will end up in emacs 23: +files you edit. If you use Emacs, customize its font-lock mode +or use its WhiteSpace mode: http://www.emacswiki.org/emacs/WhiteSpace -[that page says its version also works with emacs 21 and 22] If you use vim, add this to ~/.vimrc: let c_space_errors=1