From: Sebastian Schwarz <seschwar@gmail.com>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH v1 1/1] emacs: Kill the stderr buffer when an async process completes
Date: Sat, 25 Aug 2018 16:27:09 +0200 [thread overview]
Message-ID: <87lg8ucyiq.fsf@domain.invalid> (raw)
In-Reply-To: <m27evib3ny.fsf@dme.org>, <20180809205434.34404-1-dme@dme.org>
On 2017-10-26, David Edmondson wrote:
> After the changes to use `make-process', the Carbon port of emacs on
> macOS (often referred to as emacs-mac or the railwaycat port) will ask
> about killing the stderr buffer after any `notmuch-search':
>
> Debugger entered--Lisp error: (quit)
> yes-or-no-p("Buffer \" *notmuch-stderr*-839121\" has a running process; kill it? ")
> process-kill-buffer-query-function()
> kill-buffer(#<buffer *notmuch-stderr*-839121>)
> notmuch-start-notmuch-sentinel(#<process notmuch-search> "finished\n")
I see the same prompt whenever I call the function
notmuch-refresh-all-buffers on Ubuntu 18.04, which has GNU Emacs
25.2 and notmuch 0.26.
On 2018-08-09, David Edmondson wrote:
> On some platforms (e.g. macOS), it is necessary to add a real sentinel
> process for the error buffer used by `notmuch-start-notmuch' rather
> than a no-op sentinel.
Applying your patch fixes this for me there.
next prev parent reply other threads:[~2018-08-25 14:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-26 10:32 Carbon (macOS) port asks about killing stderr buffer David Edmondson
2017-10-30 13:32 ` David Edmondson
2018-01-31 14:54 ` David Edmondson
2018-08-09 20:54 ` [PATCH v1 1/1] emacs: Kill the stderr buffer when an async process completes David Edmondson
2018-08-25 11:59 ` David Edmondson
2018-08-25 14:27 ` Sebastian Schwarz [this message]
2018-08-26 11:30 ` David Bremner
2018-08-26 21:16 ` 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=87lg8ucyiq.fsf@domain.invalid \
--to=seschwar@gmail.com \
--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).