Date: Wed, 13 Feb 2013 14:35:35 -0800
From: "Kevin J. McCarthy" <kevin@8t8.us>
To: notmuch@notmuchmail.org
Subject: Re: notmuch-mutt: Use of uninitialized value.
Message-ID: <20130213223535.GA3258@zaogao.lan>
Mail-Followup-To: notmuch@notmuchmail.org, Profpatsch <mail@profpatsch.de>,
	Stefano Zacchiroli <zack@upsilon.cc>
References: <20130212005801.GA8419@soarin>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
	protocol="application/pgp-signature"; boundary="n8g4imXOkfNTN/H1"
Content-Disposition: inline
In-Reply-To: <20130212005801.GA8419@soarin>
OpenPGP: id=B6B1CD9613699FB8;
	url=http://www.8t8.us/configs/13699FB8.asc.pubkey; preference=sign
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: Stefano Zacchiroli <zack@upsilon.cc>, Profpatsch <mail@profpatsch.de>
Precedence: list


--n8g4imXOkfNTN/H1
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Profpatsch wrote:
> Since I don=E2=80=99t get your bug tracking system (d=E2=80=99oh ;), here=
 is a bug I
> encountered with notmuch-mutt using this macro I guess was from the
> =E2=80=9Cofficial=E2=80=9D tutorial:
>=20
> # Construct a thread ouf of the marked mail (or something like that,
> # doesn=E2=80=99t 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)"
>=20
> 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


--n8g4imXOkfNTN/H1
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQEcBAEBCAAGBQJRHBUwAAoJELaxzZYTaZ+4gJ8H/irRGy9yKR16zIACC7Waa2KJ
wOmtZJV8wNZ3VOimnDD46vidodqfFnCCXIgb6WqA57qDqVUChfU24jTbN6yaVZxn
9vhWSsR6EbjucxCIGtWlFD/11LPsfgbvPHtg0u8pEbY8pVMoUN0QGVAEisgzYFpP
Ro8x7Wu2DweZAq2lGoJoRq/4903qtRBNbmw5ltBFH2Lr/Jw5b7QTJmqcz79BXQA0
maTqcYyoX1mp4YhJVVK/yvI4gmtOZb0/El3a5UF84UzTMp/z9KwoaLPCPGNeCf1E
sYAUv0NJlkbIdRYpYOJtoPOykk4qY/tZI60zJqP5N01WPAoqMoDz5T+0Djq10nc=
=gOrS
-----END PGP SIGNATURE-----

--n8g4imXOkfNTN/H1--