From: Michael J Gruber <michaeljgruber+grubix+git@gmail.com>
To: David Bremner <david@tethera.net>
Cc: ricardomartins@riseup.net, notmuch@notmuchmail.org
Subject: Re: ## error when running notmuch from emacsclient, but not from standalone emacs instance
Date: Wed, 18 Jan 2023 15:55:35 +0100 [thread overview]
Message-ID: <CAA19uiSg6-1UcPc3Na9g4wBwLkm4jQfOhv-t6KwowtkhDL=aFA@mail.gmail.com> (raw)
In-Reply-To: <87mt6fq537.fsf@tethera.net>
Am Mi., 18. Jan. 2023 um 15:40 Uhr schrieb David Bremner <david@tethera.net>:
>
> ricardomartins@riseup.net writes:
>
> >
> > When I try to run notmuch from the emacsclient instance (M-x notmuch
> > <RET>), I get an error
> > "notmuch count --batch failed
> > Please check that the notmuch CLI is new enough to support `count
> > --batch'. In general we recommend running matching versions of
> > the CLI and emacs interface."
> >
>
> I agree it is strange strange to have problems only affecting
> emacsclient. The only thing I can think of off hand is that starting
> emacsclient does not reload the emacs initialization file, so make sure
> you run both experiments with a fresh restart of emacs.
>
> What is the output of M-x notmuch-version for both emacsclient and emacs?
... and how are you starting the emacs server? Depending on that,
server and standalone may get a different PATH from the environment so
that one uses the system notmuch and the other your personal install.
next prev parent reply other threads:[~2023-01-18 15:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 5:14 ## error when running notmuch from emacsclient, but not from standalone emacs instance ricardomartins
2023-01-18 14:39 ` David Bremner
2023-01-18 14:55 ` Michael J Gruber [this message]
2023-01-18 16:52 ` ricardomartins
2023-01-18 18:16 ` David Bremner
2023-01-18 19:43 ` tom.hirschowitz
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='CAA19uiSg6-1UcPc3Na9g4wBwLkm4jQfOhv-t6KwowtkhDL=aFA@mail.gmail.com' \
--to=michaeljgruber+grubix+git@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
--cc=ricardomartins@riseup.net \
/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).