[bug #14615] Coding rules

Update of bug #14615 (project findutils): Severity: 3 - Normal => 2 - Minor Status:None => Invalid Assigned to:None => jay Open/Closed

[bug #14615] Coding rules

Follow-up Comment #4, bug #14615 (project findutils): > Maybe I should change my .emacs configuration to add "untabify" to write-file-hooks. I wouldn't. The find code right now matches the defacto standard of mod8 tabs. This is the same as other GNU projects and is the default for emacs, vi, v

[bug #14615] Coding rules

Follow-up Comment #3, bug #14615 (project findutils): Maybe I should change my .emacs configuration to add "untabify" to write-file-hooks. ___ Reply to this item at: ___

Re: [bug #14615] Coding rules

Eric Blake wrote: 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 (o

[bug #14615] Coding rules

Follow-up Comment #2, bug #14615 (project findutils): > findutils is consistent in that \t is always treated as 8 columns > 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 Agreed. The standards only say that ho

[bug #14615] Coding rules

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 ty

[bug #14615] Coding rules

URL: Summary: Coding rules Project: findutils Submitted by: poltuiu Submitted on: jeu 22.09.2005 à 11:16 Category: None Severity: 3 - Normal