Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id 9986A431FAF for ; Sat, 21 Jan 2012 13:35:26 -0800 (PST) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id QKBvii3TFNMB for ; Sat, 21 Jan 2012 13:35:25 -0800 (PST) Received: from guru.guru-group.fi (guru-group.fi [87.108.86.66]) by olra.theworths.org (Postfix) with ESMTP id C221B431FAE for ; Sat, 21 Jan 2012 13:35:25 -0800 (PST) Received: by guru.guru-group.fi (Postfix, from userid 501) id 73F5168056; Sat, 21 Jan 2012 23:35:27 +0200 (EET) From: Tomi Ollila To: notmuch@notmuchmail.org Subject: Re: [PATCH 1/2] uncrustify.cfg: initial support for notmuch coding style In-Reply-To: <87sjj8bvvn.fsf@zancas.localnet> References: <1324135695-15487-1-git-send-email-david@tethera.net> <1326197228-10356-1-git-send-email-david@tethera.net> <1326197228-10356-2-git-send-email-david@tethera.net> <87sjj8bvvn.fsf@zancas.localnet> User-Agent: Notmuch/0.11+71~gefa5d6c (http://notmuchmail.org) Emacs/23.3.1 (x86_64-unknown-linux-gnu) X-Face: HhBM'cA~ MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 21 Jan 2012 21:35:26 -0000 On Sat, 21 Jan 2012 17:15:08 -0400, David Bremner wrote: > On Tue, 10 Jan 2012 08:07:07 -0400, David Bremner wrote: > > From: David Bremner > > > > Uncrustify is a free (as in GPL2+) tool that indents and beautifies > > C/C++ code. > > I pushed a revised version of this, with some input from Tomi. I guess > this should be documented somewhere either the wiki, under devel, or > both. Perhaps we should work on a "coding style" page on the wiki, and > then copy snapshots of that into ./devel? Or just edit a text file in > ./devel? It would be best to have the documents in ./devel and just references to those on the wiki. To avoid duplication and content drifting. That particular case: enum format_enum { NOTMUCH_FORMAT_JSON, NOTMUCH_FORMAT_TEXT } - format_sel = NOTMUCH_FORMAT_TEXT; + format_sel = NOTMUCH_FORMAT_TEXT; Is interesting, running emacs -q notmuch-search.c and tab-indenting that same line yieds the same results. However, on top-level, i.e.: enum format_enum { NOTMUCH_FORMAT_JSON, NOTMUCH_FORMAT_TEXT } format_sel = NOTMUCH_FORMAT_TEXT; emacs indents just like above. I like this suggestion: >*> enum format_enum { >*> NOTMUCH_FORMAT_JSON, NOTMUCH_FORMAT_TEXT >*> } format_sel = NOTMUCH_FORMAT_TEXT; > > d > Tomi