unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Austin Clements <amdragon@MIT.EDU>
To: David Bremner <bremner@debian.org>
Cc: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] STYLE: Initial draft of coding style document
Date: Sun, 5 Feb 2012 23:42:05 -0500	[thread overview]
Message-ID: <20120206044205.GQ10898@mit.edu> (raw)
In-Reply-To: <87vcnnjuac.fsf@rocinante.cs.unb.ca>

Quoth David Bremner on Feb 03 at  8:50 pm:
> On Mon, 30 Jan 2012 18:01:15 +0200, Jani Nikula <jani@nikula.org> wrote:
> > On Jan 30, 2012 4:38 PM, "Tomi Ollila" <tomi.ollila@iki.fi> wrote:
> > >
> > > > +
> > > > +* Indent is 4 spaces with mixed tabs/spaces and a tab width of 8.
> > > > +  Tabs should be only at the beginning of the line.
> > >
> > > So, after initial indentation (with tabs) there should not be further
> > > tabs? We'll be using the former instead of the latter in these 2 below?
> 
> Ah, I only meant to explain what whitespace-mode complains about, namely
> 
> <space><space><space><space><tab>x=1;
> 
> as opposed to 
> 
> <tab<space><space><space><space><tab>x=1;
> 
> I'm not sure it's that important, but apparently if it stays in the
> style guide it needs rewording.

Any indentation style this difficult to explain can't be a good idea.
How about,

* Indent is 4 spaces with mixed tab/spaces and a tab width of 8.
  (Specifically, a line should begin with zero or more tabs followed
  by fewer than eight spaces.)

  reply	other threads:[~2012-02-06  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 23:46 [PATCH] STYLE: Initial draft of coding style document David Bremner
2012-01-30 14:38 ` Tomi Ollila
2012-01-30 16:01   ` Jani Nikula
2012-02-04  0:50     ` David Bremner
2012-02-06  4:42       ` Austin Clements [this message]
2012-02-13  1:42         ` David Bremner
2012-02-19 20:54           ` Pieter Praet

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20120206044205.GQ10898@mit.edu \
    --to=amdragon@mit.edu \
    --cc=bremner@debian.org \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).