Mailing-List: contact dev-help@couchdb.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@couchdb.apache.org
Received-SPF: pass (athena.apache.org: domain of robert.newson@gmail.com
 designates 209.85.212.52 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :content-type:content-transfer-encoding;
        b=YNdOH17TZ6n+FI3/Efoe6vwL30V8PiFtu0osP5v8F5Nq+gxkMIFXco7B+b5tb6i+9y
         3FCRzqwg1mV/n0tsaXh2jHmve8y/kWkwv04ltpqEubeX9FLfk+G55D3WRXk/1o0hA85R
         w26lPm9TB0FT7gyMndBh/FulXn1zSmVO4YSa8=
MIME-Version: 1.0
In-Reply-To: <AANLkTimmgFt2mCscO+SG23enWP7BM4thceocUB5S29fG@mail.gmail.com>
References: <AANLkTim45jnYian4fgPRWBP72_rF-pYqK=rNw7QSChEj@mail.gmail.com>
	<AANLkTin+EQCq=pKwOSp7+39FDrHs8SWr14J7k+6w8uZG@mail.gmail.com>
	<AANLkTin=v=mE30h=_-q9tH5Bx8s4w9bG1ONQPeOkwfY+@mail.gmail.com>
	<C610A400-DC83-4D3E-A1F0-7744FC8A798F@apache.org>
	<AANLkTimmgFt2mCscO+SG23enWP7BM4thceocUB5S29fG@mail.gmail.com>
Date: Tue, 30 Nov 2010 13:34:57 +0000
Message-ID: <AANLkTikTLg1+09j+OtepWrA4FNXrpE8UJhMYnxnnekVG@mail.gmail.com>
Subject: Re: use view functions to emit changes
From: Robert Newson <robert.newson@gmail.com>
To: dev@couchdb.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Am I the only one that thinks our code is already indented to 4 spaces? :)

B.

On Tue, Nov 30, 2010 at 1:32 PM, Benoit Chesneau <bchesneau@gmail.com> wrot=
e:
> On Tue, Nov 30, 2010 at 1:50 PM, Jan Lehnardt <jan@apache.org> wrote:
>>
>> On 30 Nov 2010, at 13:05, Benoit Chesneau wrote:
>>
>>> On Tue, Nov 30, 2010 at 12:22 PM, Filipe David Manana
>>> <fdmanana@apache.org> wrote:
>>>>
>>>> 3) Avoid the unnecessary white-space only changes:
>>>>
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L2R396
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L2R477
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L3R255
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L4R60
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L4R85
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L4R247
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L4R503
>>>> https://github.com/benoitc/couchdb/commit/651e29e1bb767fb493bf75497623=
dae89bf9a5ad#L3R191
>>>
>>>
>>> about 2 & 3 can we add indent rules on top of our sources from now ?
>>> I think there is something common between vim and emacs for example.
>>> That should solve such errors. I don't want to change my config each
>>> time I'm using a project. Using such rules solves that automatically.
>>>
>>> Ex:
>>>
>>> %% -*- tab-width: 4;erlang-indent-level: 4;indent-tabs-mode: nil -*-
>>> %% ex: ts=3D4 sw=3D4 et
>>>
>>> works on erlang and vim and surely other editors.
>>
>> a) I don't mind adding these markers they it help anyone.
>> b) My editor and git tell me about trailing whitespace.
>> c) Because of b), these markers never helped me.
>>
>>> About the 2 spaces
>>> in js, imo we should go to a 4 spaces indentations, which is a way
>>> more readable and more common. (Mozilla uses that rule.)
>>
>> We agreed on two spaces early on:
>>
>> =A0http://wiki.apache.org/couchdb/Coding_Standards
>>
>> Coding standards are not to find the best one, but to pick one and
>> stick to it.
>>
> Coding standard are here to make the code more easy to share *between*
> developers, this isn't just a convention. Sorry to disagree with the 2
> spaces indentation.
>
> While we are in coding standard , there is one I really think we
> should follow "http://www.erlang.se/doc/programming_rules.shtml#REF14536"
> . I think I can add for some, but need help for btree codes and view
> server, anyone can help me on that ?
>
> - beno=EEt.
>