unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: David Bremner <david@tethera.net>
To: 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 14:16:35 -0400	[thread overview]
Message-ID: <875yd3pv24.fsf@tethera.net> (raw)
In-Reply-To: <8dae5975ad2586413e53c9c936c27d90@riseup.net>

ricardomartins@riseup.net writes:

> 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. 

I don't have personal experience with running emacs from systemd, but I
guess it could be worth trying

M-: (executable-find "notmuch")

That will verify that you are not being tripped up by multiple notmuch
executables.

Another thing to try is

M-x notmuch-search <return> tag:inbox <return>

This may give a more helpful error message (or it may work fine,
indicating the problem is really with notmuch count, but the --batch
option is almost 10 years old now, so I think that error checking
probably needs to be updated.


  reply	other threads:[~2023-01-18 18:19 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
2023-01-18 18:16       ` David Bremner [this message]
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=875yd3pv24.fsf@tethera.net \
    --to=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).