From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: bugs@gnu.support, 50849@debbugs.gnu.org
Subject: bug#50849: 28.0.50; Proposal for Emacs daemon to signal when being busy
Date: Fri, 02 Sep 2022 15:02:58 +0200 [thread overview]
Message-ID: <87sflaszct.fsf@gnus.org> (raw)
In-Reply-To: <83ilm6osqz.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 02 Sep 2022 15:39:16 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> What would be a reasonable timeout here? Say... five seconds?
>
> Too short, IMO. I'd say 10 (and expose this as a Lisp variable, so
> whoever is unhappy about the default can do what they want).
Makes sense.
But I'm slightly leery about having a default timeout at all -- I can
imagine that there are people using emacsclient as an RPC thing to
control an Emacs automatically, and in that case, any timeout would be
wrong: It's more important to have a reliable mechanism than anything
else. (And in that scenario, the Emacs daemon might well be busy for a
long time, if you have a script that just feeds commands to the
daemon...)
But on the other hand, it's nice to give the user some more feedback
there than just hanging.
Hm...
Might it make sense to use the timeout to just output a message on
stdout saying "Unable to contact the server; use `C-c' to break" or
something? Instead of just exiting/erroring out?
Anybody have opinions here?
next prev parent reply other threads:[~2022-09-02 13:02 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 14:23 bug#50849: 28.0.50; Proposal for Emacs daemon to signal when being busy Jean Louis
2021-09-27 15:27 ` Eli Zaretskii
2021-09-28 5:56 ` Lars Ingebrigtsen
2021-09-28 7:08 ` Eli Zaretskii
2022-09-02 11:09 ` Lars Ingebrigtsen
2022-09-02 11:21 ` Eli Zaretskii
2022-09-02 12:28 ` Lars Ingebrigtsen
2022-09-02 12:39 ` Eli Zaretskii
2022-09-02 12:44 ` Robert Pluim
2022-09-02 13:02 ` Lars Ingebrigtsen [this message]
2022-09-02 13:54 ` Visuwesh
2022-09-02 14:02 ` Eli Zaretskii
2022-09-03 9:48 ` Lars Ingebrigtsen
2022-09-03 15:40 ` Stefan Kangas
2022-09-03 15:57 ` Eli Zaretskii
2022-09-04 10:59 ` Lars Ingebrigtsen
2022-09-05 13:56 ` Stefan Kangas
2022-09-05 19:07 ` Lars Ingebrigtsen
2022-09-06 0:19 ` Stefan Kangas
2022-09-06 2:31 ` Eli Zaretskii
2022-09-06 3:33 ` Visuwesh
2022-09-06 12:22 ` Eli Zaretskii
2022-09-06 14:02 ` Robert Pluim
2022-09-06 14:12 ` Eli Zaretskii
2022-09-06 14:20 ` Robert Pluim
2022-09-07 1:05 ` Stefan Kangas
2022-09-07 2:39 ` Eli Zaretskii
2022-09-07 8:18 ` Stefan Kangas
2022-09-07 10:34 ` Robert Pluim
2022-09-07 11:19 ` Eli Zaretskii
2022-09-08 1:47 ` Stefan Kangas
2022-09-08 5:59 ` Eli Zaretskii
2022-09-08 12:07 ` Lars Ingebrigtsen
2022-09-08 13:42 ` Eli Zaretskii
2022-09-08 13:46 ` Lars Ingebrigtsen
2022-09-08 14:05 ` Eli Zaretskii
2022-09-08 14:11 ` Lars Ingebrigtsen
2022-09-08 14:15 ` Eli Zaretskii
2022-09-08 14:19 ` Robert Pluim
2022-09-08 16:02 ` Eli Zaretskii
2022-09-09 8:47 ` Robert Pluim
2022-09-09 9:29 ` Stefan Kangas
2022-09-09 9:35 ` Robert Pluim
2022-09-09 9:38 ` Stefan Kangas
2022-09-09 11:31 ` Eli Zaretskii
2022-09-06 8:20 ` Robert Pluim
2022-09-06 8:52 ` Lars Ingebrigtsen
2022-09-03 1:07 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-03 9:49 ` Lars Ingebrigtsen
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=87sflaszct.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=50849@debbugs.gnu.org \
--cc=bugs@gnu.support \
--cc=eliz@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).