From: ricardomartins@riseup.net
To: notmuch@notmuchmail.org
Subject: Re: ## error when running notmuch from emacsclient, but not from standalone emacs instance
Date: Wed, 18 Jan 2023 16:52:13 +0000 [thread overview]
Message-ID: <8dae5975ad2586413e53c9c936c27d90@riseup.net> (raw)
In-Reply-To: <CAA19uiSg6-1UcPc3Na9g4wBwLkm4jQfOhv-t6KwowtkhDL=aFA@mail.gmail.com>
>> What is the output of M-x notmuch-version for both emacsclient and emacs?
Both show notmuch version 0.37.
>> ... and how are you starting the emacs server?
I started as a systemd user unit. I'm using GNU Emacs 30.0.50
Development version 2f05f48918ec on master branch; build date
2023-01-07. VISUAL and EDITOR environment variables are set to
emacsclient.
>> 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.
Ok, so I tested this. I tried stopping the systemd unit of the emacs
server, opened an emacs instance, and started the server from within
emacs (M-x server-start <RET>). Connected to this server in a new frame
($ emacsclient -nc) and tried executing notmuch again (M-x notmuch
<RET>). This time, it worked like it should. So, definitely an issue
with the systemd unit method of initialization there, although it only
executes /usr/bin/emacs --fg-daemon, so I'm not sure exactly is going on
here that's causing the problem.
Thanks for helping.
next prev parent reply other threads:[~2023-01-18 16:52 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
2023-01-18 16:52 ` ricardomartins [this message]
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=8dae5975ad2586413e53c9c936c27d90@riseup.net \
--to=ricardomartins@riseup.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).