From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: mail@daniel-mendler.de, bugs@gnu.support, emacs-devel@gnu.org
Subject: Re: emacsclient in elisp
Date: Fri, 21 May 2021 18:08:05 +0300 [thread overview]
Message-ID: <83bl94m8fe.fsf@gnu.org> (raw)
In-Reply-To: <jwv8s48cf6t.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Fri, 21 May 2021 10:55:02 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: mail@daniel-mendler.de, bugs@gnu.support, emacs-devel@gnu.org
> Date: Fri, 21 May 2021 10:55:02 -0400
>
> > Btw: in batch mode, read-from-minibuffer returns when it sees a
> > newline, so you could still use the above if you'd process each
> > incoming line, and then issued another read-from-minibuffer call only
> > when the processing was done.
>
> The next line may not come from another half-hour, or even "for ever" if
> the other side is waiting for our (asynchronous) answer before sending the
> next command.
So don't call read-from-minibuffer until you have processed the
previous job and sent out the results.
> > So the situation we have doesn't look too bad to me.
>
> There are cases where it's usable, but there are cases where it's
> a non-starter.
Why focus on the latter?
next prev parent reply other threads:[~2021-05-21 15:08 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
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 [this message]
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=83bl94m8fe.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.