unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: notmuch@notmuchmail.org
Subject: [bug?] emacs interface - some mark read tag changes may have failed
Date: Mon, 06 Jun 2022 13:01:24 +0200	[thread overview]
Message-ID: <87bkv6kqd7.fsf@xelera.eu> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 975 bytes --]

Hello,

I use notmuch via emacs since long ago (at least 3 years) and all is
working great

...except today I received a message (reply) that emacs-notmuch have
problems showing, if I try to open it (press return on the message in
the notmuch-search buffer) it hangs forever and I can just interrupt
the notmuch-show command using CTRL-g; after I press CTRL-g I get this
text in the buffer:

  [some mark read tag changes may have failed]

I launched emacs with:

  emacs -Q --eval "(require 'notmuch)"

If I

  notmuch show --format=raw id:26ee39e3-fa3a-52f3-1a3f-0d222e2613f8@di.unimi.it

in a terminal I get the whole message with no errors, so I think it
should be an emacs interface error

how can I debug this kind of errors?

is there a way i can reply to the affected email dumping the raw message in
a text file and using it with emacs as if it's a "normal message"?

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 849 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2022-06-06 11:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-06 11:01 Giovanni Biscuolo [this message]
2022-06-06 12:12 ` [bug?] emacs interface - some mark read tag changes may have failed David Bremner
2022-06-06 13:18   ` Giovanni Biscuolo
2022-06-06 13:57     ` David Bremner
2022-06-06 18:07       ` Giovanni Biscuolo
2022-06-07  9:57         ` David Bremner
2022-06-07 13:13           ` Giovanni Biscuolo

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=87bkv6kqd7.fsf@xelera.eu \
    --to=g@xelera.eu \
    --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).