Sender: suvayu ali <fatkasuvayu@gmail.com>
Date: Fri, 15 Feb 2013 03:45:35 +0100
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: notmuch-mutt: Use of uninitialized value.
Message-ID: <20130215024535.GA3423@kuru.dyndns-at-home.com>
Mail-Followup-To: notmuch@notmuchmail.org, Stefano Zacchiroli
 <zack@upsilon.cc>
References: <20130212005801.GA8419@soarin> <20130213223535.GA3258@zaogao.lan>
	<20130213233657.GA4489@soarin> <20130214083713.GA4123@upsilon.cc>
	<20130214230651.GA3247@zaogao.lan>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130214230651.GA3247@zaogao.lan>
User-Agent: Mutt/1.5.21 (2012-12-30)
Cc: Stefano Zacchiroli <zack@upsilon.cc>
Precedence: list

Hi Kevin and others,

On Thu, Feb 14, 2013 at 03:06:51PM -0800, Kevin J. McCarthy wrote:
> 
> Here are some proposed improved macros.  (I'll attach a patch file in
> another email.)  Despite my earlier warning about not line-breaking
> macros, these are getting a bit unreadable.  We may want to see
> if/where we can safely line-break them.

I find sticking by the rule "do not introduce whitespaces to make it
readable" very useful in multi-line macros.  For example,

macro index <key> "<some-long-function>some text<another-function>\
continuation<finally-the-end>"

the above is preferable over,

macro index <key> "<some-long-function>some text<another-function> \
                   continuation<finally-the-end>"

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.