From: Eli Zaretskii <eliz@gnu.org>
To: Daniel Mendler <mail@daniel-mendler.de>
Cc: monnier@iro.umontreal.ca, bugs@gnu.support, emacs-devel@gnu.org
Subject: Re: emacsclient in elisp
Date: Fri, 21 May 2021 09:16:19 +0300 [thread overview]
Message-ID: <838s48obm4.fsf@gnu.org> (raw)
In-Reply-To: <2db11dcb-d3ce-ae40-c6ea-5746c686da8b@daniel-mendler.de> (message from Daniel Mendler on Thu, 20 May 2021 22:54:45 +0200)
> Cc: monnier@iro.umontreal.ca, bugs@gnu.support, emacs-devel@gnu.org
> From: Daniel Mendler <mail@daniel-mendler.de>
> Date: Thu, 20 May 2021 22:54:45 +0200
>
> On 5/20/21 9:45 PM, Eli Zaretskii wrote:
> > But then I don't understand the importance of stdin in this context.
> > If you want to read output from another program, just run that
> > program, in this case another Emacs, as a subprocess. Then anything
> > that other program writes to its stdout will be read as part of normal
> > machinery of reading sub-process output, including filters, sentinels,
> > and all that.
>
> Yes, that's right. I have two Emacs processes A and B. The process A
> starts process B as subprocess and communicates with it via the pipe.
> The process B reads from the stdin using `(read t)` or
> `(read-from-minibuffer..)`. Now process B starts another subprocess C,
> which has a filter and a sentinel. While B reads from stdin, B hangs and
> the C-filter is not executed.
The same will happen if B runs some Lisp function that takes a long
time.
> Alternatively one can use network streams. A creates a server, B creates
> a client and then they communicate asynchronously, B can start a
> subprocess C and the AB-network communication does not impede the
> subprocess C.
So you already have a solution for such use cases, right? Then what
would be the advantage of doing the same via stdin?
> I would like to offload work from Emacs to sub-Emacs processes which are
> connected via some IPC protocol. I am currently using the emacsclient
> protocol for this (with some custom extensions). Stefan suggested that
> it may be better if the Emacs processes communicate directly using
> pipes. But given the stdin blocking problem, described above, this is
> not possible.
Then I guess it is Stefan who should answer the question above.
> Actually I am happy with using the emacsclient protocol now. It is a bit
> of a hack, but it works for the simple use case I am currently exploring
I don't see why it would be considered a hack. Using the emacsclient
_protocol_ might be considered a kludge, but you can use your own
protocol, and then I see no kludge at all in this design.
> (https://github.com/minad/affe). There I have Emacs A (frontend)
> starting an Emacs B (backend) which starts grep as a subprocess C,
> generating output. Then A sends filter regular expressions to B, B
> filters the output of C and answers with the matches.
Not sure why you need Grep in this equation at all: Emacs is perfectly
capable of searching files entirely on its own, and since your design
is asynchronous, speed should not matter too much anyway.
next prev parent reply other threads:[~2021-05-21 6:16 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-19 12:50 emacsclient in elisp Daniel Mendler
2021-05-19 13:41 ` Stefan Monnier
2021-05-19 14:13 ` Daniel Mendler
2021-05-19 14:55 ` T.V Raman
2021-05-20 14:31 ` Jean Louis
2021-05-20 15:10 ` Eli Zaretskii
2021-05-20 15:52 ` Daniel Mendler
2021-05-20 16:00 ` Eli Zaretskii
2021-05-20 16:40 ` Stefan Monnier
2021-05-20 17:49 ` Daniel Mendler
2021-05-20 18:59 ` Eli Zaretskii
2021-05-20 19:10 ` Daniel Mendler
2021-05-20 19:45 ` Eli Zaretskii
2021-05-20 20:54 ` Daniel Mendler
2021-05-21 6:16 ` Eli Zaretskii [this message]
2021-05-21 10:33 ` Daniel Mendler
2021-05-21 10:44 ` Eli Zaretskii
2021-05-21 16:25 ` Jean Louis
2021-05-21 6:38 ` Jean Louis
2021-05-21 6:36 ` Jean Louis
2021-05-21 7:10 ` Eli Zaretskii
2021-05-20 21:21 ` Stefan Monnier
2021-05-21 6:18 ` Eli Zaretskii
2021-05-21 10:34 ` Eli Zaretskii
2021-05-21 14:55 ` Stefan Monnier
2021-05-21 15:08 ` Eli Zaretskii
2021-05-21 15:33 ` Stefan Monnier
2021-05-21 14:51 ` Stefan Monnier
2021-05-21 15:06 ` Eli Zaretskii
2021-05-21 15:29 ` Stefan Monnier
2021-05-21 18:36 ` Eli Zaretskii
2021-05-21 21:51 ` Stefan Monnier
2021-05-22 6:11 ` Eli Zaretskii
2021-05-22 10:09 ` Daniel Mendler
2021-05-22 10:19 ` Eli Zaretskii
2021-05-22 10:29 ` Eli Zaretskii
2021-05-22 11:49 ` Daniel Mendler
2021-05-22 12:26 ` Eli Zaretskii
2021-05-22 13:55 ` Stefan Monnier
2021-05-22 14:08 ` Eli Zaretskii
2021-05-22 14:31 ` Stefan Monnier
2021-05-21 16:10 ` Daniel Mendler
2021-05-21 16:36 ` Jean Louis
2021-05-21 6:27 ` Jean Louis
2021-05-21 7:07 ` Eli Zaretskii
2021-05-21 7:25 ` Jean Louis
2021-05-21 6:21 ` Jean Louis
2021-05-21 7:08 ` Eli Zaretskii
2021-05-21 7:26 ` Jean Louis
2021-05-21 10:31 ` Eli Zaretskii
2021-05-21 16:07 ` Jean Louis
2021-05-21 17:41 ` Eli Zaretskii
2021-05-21 17:43 ` Eli Zaretskii
2021-05-21 22:05 ` Jean Louis
2021-05-22 6:12 ` Eli Zaretskii
2021-05-19 21:56 ` Daniel Mendler
2021-05-19 22:43 ` chad
2021-05-20 8:42 ` Daniel Mendler
2021-05-20 15:59 ` Arthur Miller
2021-05-20 17:45 ` Daniel Mendler
2021-05-21 19:52 ` Arthur Miller
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838s48obm4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bugs@gnu.support \
--cc=emacs-devel@gnu.org \
--cc=mail@daniel-mendler.de \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.