From: David Bremner <david@tethera.net>
To: david wen riccardi-zhu <dwrz@dwrz.net>
Cc: notmuch@notmuchmail.org
Subject: Re: Emacs "notmuch CLI version mismatch"
Date: Mon, 10 Jul 2017 17:40:04 -0300 [thread overview]
Message-ID: <87shi410wr.fsf@tethera.net> (raw)
In-Reply-To: <9ed487a8f4028c7271ec7150b04f6ce5@dwrz.net>
david wen riccardi-zhu <dwrz@dwrz.net> writes:
> Thanks so much, David.
>
>> At a guess, you are using git master of the emacs client (perhaps via
>> melpa, or via some arch git snapshot package), and a released version of
>> the notmuch binary.
>
> I am using MELPA -- does this mean I should be using git to get the
> binary?
I don't see the advantage of using melpa for notmuch. You need notmuch
binaries, and you want them to match the version of your emacs code. So
wherever you get your notmuch binaries from (whether arch, or building
from source) should also be your source of the notmuch emacs code. But
yes, if you insist on using melpa for notmuch-emacs, you should track
the git versions of the notmuch binaries (at least you should update to
current git whenever you get version mismatch messages from the emacs
client).
>> What is the output of M-x notmuch-hello-versions <return>
>
> notmuch version 0.24.2
>
That's very suprising, since it should also print the version of notmuch
emacs mua if it is different from the notmuch version.
next prev parent reply other threads:[~2017-07-10 20:40 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 12:16 Emacs "notmuch CLI version mismatch" david wen riccardi-zhu
2017-07-10 18:14 ` David Bremner
2017-07-10 19:22 ` david wen riccardi-zhu
2017-07-10 20:40 ` David Bremner [this message]
2017-07-10 21:12 ` David Edmondson
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=87shi410wr.fsf@tethera.net \
--to=david@tethera.net \
--cc=dwrz@dwrz.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).