This is obviously incomplete (the FIXME, and no configuration
recommendations for Emacs' Whitespace), but we have to start somewhere.
As usual, suggestions welcome.

>From d88c9f95e38cb86460ba4acaf90b24c3c8fce8bf Mon Sep 17 00:00:00 2001
From: Jim Meyering <>
Date: Wed, 25 Feb 2009 15:37:58 +0100
Subject: [PATCH] * HACKING: avoid trailing white space

 HACKING |   24 ++++++++++++++++++++++++
 1 files changed, 24 insertions(+), 0 deletions(-)

diff --git a/HACKING b/HACKING
index bf9a45e..0675f9c 100644
@@ -356,6 +356,30 @@ With other files, there will be some existing differences.
 Try not to add any more.

+Avoid trailing white space
+You may notice that the only trailing blanks in coreutils'
+version-controlled files are in a single directory: tests/pr,
+which contains expected output from various invocations of pr.
+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:
+[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
+    highlight RedundantSpaces ctermbg=red guibg=red
+    match RedundantSpaces /\s\+$\| \+\ze\t/

 Miscellaneous useful git commands

Bug-coreutils mailing list

Reply via email to