unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Kevin J. McCarthy" <kevin@8t8.us>
To: notmuch@notmuchmail.org
Cc: Stefano Zacchiroli <zack@upsilon.cc>, Profpatsch <mail@profpatsch.de>
Subject: Re: notmuch-mutt: Use of uninitialized value.
Date: Wed, 13 Feb 2013 14:35:35 -0800	[thread overview]
Message-ID: <20130213223535.GA3258@zaogao.lan> (raw)
In-Reply-To: <20130212005801.GA8419@soarin>

[-- Attachment #1: Type: text/plain, Size: 1425 bytes --]

Profpatsch wrote:
> Since I don’t get your bug tracking system (d’oh ;), here is a bug I
> encountered with notmuch-mutt using this macro I guess was from the
> “official” tutorial:
> 
> # Construct a thread ouf of the marked mail (or something like that,
> # doesn’t work atm (errors out))
>     macro index <F9> \
>         "<enter-command>unset wait_key<enter><pipe-message> \
> 	/usr/bin/notmuch-mutt thread<enter><change-folder-readonly> \
> 	~/.cache/notmuch/mutt/results/<enter> \
> 	<enter-command>set wait_key<enter>" \
> 	                "search and reconstruct owning thread (using
> 			notmuch)"
> 
> I hope this still works, best to put it on one line I guess.

Mutt macros can behave strangely if you try to break them into multiple
lines.  So my first suggestion is to try setting your macro to exactly
how it's shown in the tutorial and see if that fixes the problem.  (I
admit that this is not likely your problem though, as notmuch-mutt is
running...)

A more likely idea is to check whether you have $pipe_decode set.
If you have this set, you need to make sure you are not weeding out
message-id with 'ignore'.

In fact, I've just tried this, and I can replicate the problem and exact
error messages with these settings:

  set pipe_decode
  ignore *
  unignore From Date To Cc Bcc Subject

Adding this will fix the problem:
  unignore Message-ID

-Kevin


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]

  parent reply	other threads:[~2013-02-13 22:35 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 [this message]
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
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=20130213223535.GA3258@zaogao.lan \
    --to=kevin@8t8.us \
    --cc=mail@profpatsch.de \
    --cc=notmuch@notmuchmail.org \
    --cc=zack@upsilon.cc \
    /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).