From: Florian Friesdorf <flo@chaoflow.net>
To: Andreas Amann <a.amann@ucc.ie>, Notmuch Mail <notmuch@notmuchmail.org>
Subject: Re: Problem with "Unexpected output" messages
Date: Sun, 17 Apr 2011 17:56:21 +0200 [thread overview]
Message-ID: <87d3kkdg7u.fsf@eve.chaoflow.net> (raw)
In-Reply-To: <8739ljwy7z.fsf@msstf091.ucc.ie>
[-- Attachment #1: Type: text/plain, Size: 1050 bytes --]
On Fri, 15 Apr 2011 12:28:00 +0100, Andreas Amann <a.amann@ucc.ie> wrote:
> On Wed, 06 Apr 2011 20:23:17 +0100, Andreas Amann <a.amann@ucc.ie> wrote:
> >
> > since commit 44d3c57e (emacs: Display any unexpected output from notmuch
> > search) I see a number of messages of the form
> >
> > Error: Unexpected output from notmuch search:
> > thread:000000000000XXXX
> >
> > after notmuch-search in emacs.
>
> FWIW, the patch below solves the problem for me.
Thx, the patch enables display and handling of a message with which I
had the same problem.
In the message list (emacs UI) the subject now shows as:
foo?
When showing the mail, the buffer name is:
foo^J
and there is an empty line in the header part as the control character
is still present:
Subject: foo
To: my@email
Date: ...
Could/should this also be changed?
--
Florian Friesdorf <flo@chaoflow.net>
GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
Jabber/XMPP: flo@chaoflow.net
IRC: chaoflow on freenode,ircnet,blafasel,OFTC
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
next prev parent reply other threads:[~2011-04-17 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-06 19:23 Problem with "Unexpected output" messages Andreas Amann
2011-04-15 11:28 ` Andreas Amann
2011-04-17 15:56 ` Florian Friesdorf [this message]
2011-04-18 8:04 ` Andreas Amann
2011-04-17 17:24 ` Pieter Praet
-- strict thread matches above, loose matches on Subject: below --
2011-05-07 9:20 Pieter Praet
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=87d3kkdg7u.fsf@eve.chaoflow.net \
--to=flo@chaoflow.net \
--cc=a.amann@ucc.ie \
--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).