From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: mail@daniel-mendler.de, emacs-devel@gnu.org
Subject: Re: emacsclient in elisp
Date: Sat, 22 May 2021 17:08:29 +0300 [thread overview]
Message-ID: <83tumukgiq.fsf@gnu.org> (raw)
In-Reply-To: <jwv35ue98t0.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 22 May 2021 09:55:20 -0400)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Daniel Mendler <mail@daniel-mendler.de>, emacs-devel@gnu.org
> Date: Sat, 22 May 2021 09:55:20 -0400
>
> > What do you mean by "at the same time"? If I have a stdin-process
> > active, we watch it via pselect and read from it using the machinery
> > in wait_reading_process_output and accept-process-output. During all
> > the time such a process is active, I see no way to also read from the
> > same descriptor bypassing the above mechanisms, in a way that won't
> > cause trouble on the Lisp level, due toe the basic inability to decide
> > which input should go what way.
>
> AFAIK we watch this description only when we're inside
> "wait_reading_process_output and accept-process-output". If we're
> inside `read-from-minibuffer` then we're not inside
> "wait_reading_process_output and accept-process-output" (and
> vice-versa), so I don't think there should be much trouble (at least for
> my understanding of POSIX file descriptors, which is admittedly somewhat
> limited; for Windows, I have no idea).
So we will enter read-from-minibuffer, and read the stuff from stdin
till the first newline. How do we know what's there is for us, not
for the stdin-process?
The scenario is that we have the process for reading from stdin, but
some function we called decides to ask the user.
next prev parent reply other threads:[~2021-05-22 14: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
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 [this message]
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=83tumukgiq.fsf@gnu.org \
--to=eliz@gnu.org \
--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.