From 133d46dcc7348356ac3bf12a1d34d5bc79c7942b Mon Sep 17 00:00:00 2001 From: Slava Zanko Date: Thu, 25 Feb 2010 14:15:20 +0200 Subject: [PATCH] Ticket #172: Use 'indent' utility Proposed options to indent: * --gnu-style * --format-first-column-comments * --indent-level4 * --brace-indent0 * --line-length100 * --no-tabs * --blank-lines-after-procedures Signed-off-by: Slava Zanko --- doc/HACKING | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/doc/HACKING b/doc/HACKING index 9fcf9d449..b09e518fb 100644 --- a/doc/HACKING +++ b/doc/HACKING @@ -86,7 +86,17 @@ that is not default for GNU Indent. Please put following text to your ~/.indent.pro file to make GNU Indent follow the style used in GNU Midnight Commander: --kr -i4 -pcs -psl --ignore-newlines +--gnu-style +--format-first-column-comments +--indent-level4 +--brace-indent0 +--line-length100 +--no-tabs +--blank-lines-after-procedures + +or in short notation: + +indent -gnu -fc1 -i4 -bli0 -nut -bap -l100 It's OK to indent the whole function if you edit it. However, please refrain from it if you are posting your patch for review. In this case