From: sbaugh@catern.com
To: emacs-devel@gnu.org
Subject: Re: call-process should not block process filters from running
Date: Tue, 04 Jul 2023 14:12:01 -0400 [thread overview]
Message-ID: <875y6zo8b2.fsf@catern.com> (raw)
In-Reply-To: 1f5d7e77-3ac0-6b6e-9bd6-73302114ebaa@gutov.dev
Dmitry Gutov <dmitry@gutov.dev> writes:
> On 03/07/2023 03:02, sbaugh@catern.com wrote:
>> Since project-find-regexp can
>> take many seconds on large repos, I think this is useful.
>> However, my other main test case/use case, being able to paste while
>> Emacs is in call-process, doesn't work with this change. Any idea on
>> how to make that work?
>
> Do you have some particular aim related to project-find-regexp?
>
> Having Emacs interactive and responsive while the search is ongoing
> would require a different direction in design.
>
> Is the goal simply to have other, unrelated code keep running?
I merely use project-find-regexp as an example of an important function
that uses call-process. The goal is indeed simply to have other
unrelated code keep running. And to be able to paste in other X
clients. And be able to call project-find-regexp (and other
call-process using functions) from a Lisp thread.
Changing project-find-regexp to use asynchronous processes would be
nice, but more work, requiring more design effort. Running processes
synchronously is fine, if it doesn't block unrelated code.
next prev parent reply other threads:[~2023-07-04 18:12 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-27 21:55 call-process should not block process filters from running Spencer Baugh
2023-06-28 11:39 ` Mattias Engdegård
2023-06-28 11:56 ` Po Lu
2023-06-28 12:08 ` Spencer Baugh
2023-06-28 13:17 ` Po Lu
2023-06-28 12:52 ` Eli Zaretskii
2023-06-28 13:27 ` Spencer Baugh
2023-06-28 13:34 ` Eli Zaretskii
2023-07-01 18:24 ` Spencer Baugh
2023-07-01 18:59 ` Eli Zaretskii
2023-07-01 19:17 ` Spencer Baugh
2023-07-02 5:45 ` Eli Zaretskii
2023-07-03 0:02 ` sbaugh
2023-07-03 10:00 ` Po Lu
2023-07-03 17:53 ` sbaugh
2023-07-03 18:51 ` Eli Zaretskii
2023-07-03 20:28 ` sbaugh
2023-07-04 4:12 ` Po Lu
2023-07-04 11:25 ` Eli Zaretskii
2023-07-04 12:42 ` sbaugh
2023-07-04 13:42 ` Michael Albinus
2023-07-04 14:16 ` sbaugh
2023-07-05 6:36 ` Michael Albinus
2023-07-04 11:10 ` Eli Zaretskii
2023-07-04 12:20 ` sbaugh
2023-07-04 13:09 ` Eli Zaretskii
2023-07-04 13:37 ` sbaugh
2023-07-04 13:25 ` Po Lu
2023-07-04 1:04 ` sbaugh
2023-07-04 4:09 ` Po Lu
2023-07-04 12:27 ` sbaugh
2023-07-04 13:22 ` Po Lu
2023-07-04 13:51 ` sbaugh
2023-07-04 16:38 ` Eli Zaretskii
2023-07-04 16:53 ` sbaugh
2023-07-04 17:14 ` Eli Zaretskii
2023-07-04 16:49 ` Dmitry Gutov
2023-07-04 18:12 ` sbaugh [this message]
2023-07-05 18:53 ` Dmitry Gutov
2023-07-06 2:24 ` sbaugh
2023-07-06 8:06 ` Michael Albinus
2023-07-08 15:54 ` sbaugh
2023-07-09 9:04 ` Michael Albinus
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875y6zo8b2.fsf@catern.com \
--to=sbaugh@catern.com \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).