From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: notmuch-mutt: Use of uninitialized value.
Date: Thu, 14 Feb 2013 10:13:36 +0100 [thread overview]
Message-ID: <20130214091336.GB21133@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <20130214083713.GA4123@upsilon.cc>
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.
next prev parent reply other threads:[~2013-02-14 9:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 0:58 notmuch-mutt: Use of uninitialized value Profpatsch
2013-02-12 16:27 ` Stefano Zacchiroli
[not found] ` <20130212165531.GA5030@soarin.rz.uni-augsburg.de>
2013-02-12 20:29 ` Stefano Zacchiroli
[not found] ` <20130212215105.GA16646@soarin>
2013-02-13 16:26 ` Stefano Zacchiroli
2013-02-13 18:08 ` Profpatsch
2013-02-13 22:35 ` Kevin J. McCarthy
2013-02-13 23:36 ` Profpatsch
2013-02-14 8:17 ` Andrei POPESCU
2013-02-14 8:37 ` Stefano Zacchiroli
2013-02-14 9:13 ` Suvayu Ali [this message]
2013-02-14 14:13 ` Profpatsch
2013-02-14 19:53 ` [OT] mutt configuration & philosophy (was Re: notmuch-mutt: Use of uninitialized value.) Michael Elkins
2013-02-14 22:59 ` David Bremner
2013-02-14 23:06 ` notmuch-mutt: Use of uninitialized value Kevin J. McCarthy
2013-02-15 2:45 ` Suvayu Ali
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=20130214091336.GB21133@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@gmail.com \
--cc=notmuch@notmuchmail.org \
/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).