Sender: suvayu ali <fatkasuvayu@gmail.com>
Date: Thu, 14 Feb 2013 10:13:36 +0100
From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: notmuch-mutt: Use of uninitialized value.
Message-ID: <20130214091336.GB21133@kuru.dyndns-at-home.com>
Mail-Followup-To: notmuch@notmuchmail.org
References: <20130212005801.GA8419@soarin> <20130213223535.GA3258@zaogao.lan>
	<20130213233657.GA4489@soarin> <20130214083713.GA4123@upsilon.cc>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20130214083713.GA4123@upsilon.cc>
User-Agent: Mutt/1.5.21 (2012-12-30)
Precedence: list

On Thu, Feb 14, 2013 at 09:37:13AM +0100, Stefano Zacchiroli wrote:
> 
> I guess it would also be nice to actually disable $pipe_decode in the
> relevant Mutt macros, but I'm not sure about to do that without
> interfering with user desired configuration. Kevin: do you know if there
> is a common Mutt trick to store the value of a variable before changing
> it, and restoring it a posteriori?  More isolation for this kind of
> things in Mutt would definitely be welcome...

This should work:

"<enter-command>set my_var=$var<enter><enter-command>unset var<enter>\
<do-your-stuff>\
<enter-command>set var=$my_var<enter>"

Hope this helps,

-- 
Suvayu

Open source is the future. It sets us free.