From: YUE Daian <sheepduke@gmail.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: BUG: Backward compatibility breakage by --sort argument
Date: Sun, 15 Aug 2021 16:05:01 +0800 [thread overview]
Message-ID: <87fsvbgmky.fsf@home.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87r1ev96mh.fsf@tethera.net>
On 2021-08-14 12:19, David Bremner <david@tethera.net> wrote:
> YUE Daian <sheepduke@gmail.com> writes:
>
>> Hi Notmuch mail list,
>>
>> I noticed that the Emacs notmuch tree stopped working after a recent (?)
>> upgrade.
>>
>
> I think the most we could do is have notmuch-emacs print a more
> informative message telling the user to upgrade notmuch (patches for
> that would be welcome; I haven't decided if it makes sense to bump the
> notmuch schema version).
>
> Quoting https://melpa.org/#/notmuch
>
> Note for MELPA users (and others tracking the development version
> of notmuch-emacs):
>
> This emacs package needs a fairly closely matched version of the
> notmuch program. If you use the MELPA version of notmuch.el (as
> opposed to MELPA stable), you should be prepared to track the
> master development branch (i.e. build from git) for the notmuch
> program as well. Upgrading notmuch-emacs too far beyond the notmuch
> program can CAUSE YOUR EMAIL TO STOP WORKING.
>
> TL;DR: notmuch-emacs from MELPA and notmuch from distro packages is
> NOT SUPPORTED.
>
Maybe check version compatibility when notmuch is invoked from Emacs?
So the user (like me) immediately know that it is time to upgrade my
system...
next prev parent reply other threads:[~2021-08-15 8:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-14 15:03 BUG: Backward compatibility breakage by --sort argument YUE Daian
2021-08-14 19:19 ` David Bremner
2021-08-15 8:05 ` YUE Daian [this message]
2021-08-15 15:52 ` David Bremner
2021-08-17 6:01 ` Tomi Ollila
2021-08-17 19:17 ` David Bremner
2021-08-22 0:00 ` [PATCH] CLI: define and use format version 5 David Bremner
2021-08-22 7:29 ` Tomi Ollila
2021-08-22 14:28 ` David Bremner
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=87fsvbgmky.fsf@home.i-did-not-set--mail-host-address--so-tickle-me \
--to=sheepduke@gmail.com \
--cc=david@tethera.net \
--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).