From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id 154606DE2580 for ; Mon, 10 Jul 2017 13:40:08 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UYry_P2nVpwd for ; Mon, 10 Jul 2017 13:40:07 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id 300746DE2542 for ; Mon, 10 Jul 2017 13:40:07 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dUfQH-0004jj-BN; Mon, 10 Jul 2017 16:36:49 -0400 Received: (nullmailer pid 10509 invoked by uid 1000); Mon, 10 Jul 2017 20:40:04 -0000 From: David Bremner To: david wen riccardi-zhu Cc: notmuch@notmuchmail.org Subject: Re: Emacs "notmuch CLI version mismatch" In-Reply-To: <9ed487a8f4028c7271ec7150b04f6ce5@dwrz.net> References: <87o9ssjxl1.fsf@dwrz.net> <87y3rw17ny.fsf@tethera.net> <9ed487a8f4028c7271ec7150b04f6ce5@dwrz.net> Date: Mon, 10 Jul 2017 17:40:04 -0300 Message-ID: <87shi410wr.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Jul 2017 20:40:08 -0000 david wen riccardi-zhu 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 > > 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.