[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #14615] Coding rules
From: |
Eric Blake |
Subject: |
[bug #14615] Coding rules |
Date: |
Thu, 22 Sep 2005 18:34:36 -0600 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6 |
Follow-up Comment #1, bug #14615 (project findutils):
The GNU Coding Standards,
http://www.gnu.org/prep/standards/standards.html#Formatting, specify how
many columns in each open brace must appear (2 column indent for every
indentation, and braces are indented on the next line, leading to the typical
4 column increase between levels of braces). Beyond that, it is silent
whether a program must use spaces or tab characters, as long as it is
consistent. findutils is consistent in that \t is always treated as 8
columns, in part inspired by the GNU emacs c-code-mode, as well as GNU
indent, which both clean up whitespace (on save, 8 consecutive leading spaces
are turned into a tab) in this manner to reduce the size of files. If your
editor cannot properly be configured to treat tab characters as eight
columns, then I would argue it is a bug in your editor, and not in
findutils.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?func=detailitem&item_id=14615>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/