From: Eli Zaretskii <eliz@gnu.org>
To: "Daniel Pettersson" <daniel@dpettersson.net>,
"João Távora" <joaotavora@gmail.com>
Cc: jurgen.de-backer.ext@eurocontrol.int, 74338@debbugs.gnu.org
Subject: bug#74338: 29.1; JSON RPC timeout too short in some cases
Date: Sat, 23 Nov 2024 15:26:33 +0200 [thread overview]
Message-ID: <86plmmkrna.fsf@gnu.org> (raw)
In-Reply-To: <m2zflqssqz.fsf@dpettersson.net> (message from Daniel Pettersson on Sat, 23 Nov 2024 01:23:16 +0100)
> From: Daniel Pettersson <daniel@dpettersson.net>
> Cc: Jurgen De Backer <jurgen.de-backer.ext@eurocontrol.int>,
> 74338@debbugs.gnu.org
> Date: Sat, 23 Nov 2024 01:23:16 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> Date: Wed, 13 Nov 2024 12:43:20 +0000
> >> From: Jurgen De Backer via "Bug reports for GNU Emacs,
> >> the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
> >>
> >>
> >> Hi,
> >> When using emacs together with eglot/ada_language_server,
> >> some requests may take longer than the 10 seconds specified in
> >> jsonrpc.el (defconst jsonrpc-default-request-timeout 0).
> >> It would be better to be able to change this default value.
> >
> > Daniel, any comments or suggestions? Maybe we should make that
> > variable a defcustom?
>
> No real harm in converting it, it might be better of it was configured
> on eglot as eglot-default-request-timeout but that would require some
> work in eglot I believe. The argument against it is that it could
> have unintended consequences for other users of jsonrpc, but I think
> it's something we can live with.
João, any reasons not to make this variable a defcustom?
next prev parent reply other threads:[~2024-11-23 13:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-13 12:43 bug#74338: 29.1; JSON RPC timeout too short in some cases Jurgen De Backer via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-14 7:43 ` Eli Zaretskii
2024-11-23 0:23 ` Daniel Pettersson
2024-11-23 13:26 ` Eli Zaretskii [this message]
2024-11-23 19:53 ` João Távora
2024-11-23 20:16 ` Eli Zaretskii
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=86plmmkrna.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74338@debbugs.gnu.org \
--cc=daniel@dpettersson.net \
--cc=joaotavora@gmail.com \
--cc=jurgen.de-backer.ext@eurocontrol.int \
/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).