From: David Bremner <david@tethera.net>
To: Giovanni Biscuolo <g@xelera.eu>, notmuch@notmuchmail.org
Subject: Re: [bug?] emacs interface - some mark read tag changes may have failed
Date: Mon, 06 Jun 2022 09:12:59 -0300 [thread overview]
Message-ID: <87ilpeuh10.fsf@tethera.net> (raw)
In-Reply-To: <87bkv6kqd7.fsf@xelera.eu>
Giovanni Biscuolo <g@xelera.eu> writes:
> after I press CTRL-g I get this text in the buffer:
> [some mark read tag changes may have failed]
This is essentially notmuch-emacs complaining that it was interrupted,
so not really telling us about the underlying issue.
>
> I launched emacs with:
>
> emacs -Q --eval "(require 'notmuch)"
>
To be honest, I'm a bit surprised this works. How does emacs find
notmuch.el in this case? Or did you maybe mean emacs -q?
> how can I debug this kind of errors?
>
I suggest using M-x toggle-debug-on-quit, so that you get a traceback.
It may help to specify versions of notmuch and emacs when reporting problems.
> 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"?
>
If you can get the text you want, then you can copy and paste it into a
message composition buffer (e.g. from C-x m). notmuch show --format=text
may offer your best bet of recovering message text.
d
next prev parent reply other threads:[~2022-06-06 12:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 11:01 [bug?] emacs interface - some mark read tag changes may have failed Giovanni Biscuolo
2022-06-06 12:12 ` David Bremner [this message]
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=87ilpeuh10.fsf@tethera.net \
--to=david@tethera.net \
--cc=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).