From: Eli Zaretskii <eliz@gnu.org>
To: Sean Whitton <spwhitton@spwhitton.name>
Cc: 60592@debbugs.gnu.org
Subject: bug#60592: 30.0.50; emacsclient: exit with a different code when the request times out
Date: Fri, 06 Jan 2023 20:12:45 +0200 [thread overview]
Message-ID: <83zgavttuq.fsf@gnu.org> (raw)
In-Reply-To: <877cxzmtq9.fsf@melete.silentflame.com> (message from Sean Whitton on Fri, 06 Jan 2023 10:57:18 -0700)
> From: Sean Whitton <spwhitton@spwhitton.name>
> Cc: 60592@debbugs.gnu.org
> Date: Fri, 06 Jan 2023 10:57:18 -0700
>
> Hello,
>
> On Fri 06 Jan 2023 at 09:37AM +02, Eli Zaretskii wrote:
>
> >> From: Sean Whitton <spwhitton@spwhitton.name>
> >> Date: Thu, 05 Jan 2023 22:47:49 -0700
> >>
> >> When calling 'emacsclient --timeout N --eval' from scripts, it would be
> >> nice if you could determine for sure when a failure was just due to a
> >> timeout, rather than, say, a Lisp exception.
> >>
> >> inotifywait(1) exits with code 2 to indicate a timeout.
> >> emacsclient could do the same.
> >
> > It would be more portable to have the exception handler send a special
> > message to emacsclient, so that it would know the reason without
> > guessing.
>
> I think this is wholly complimentary to what I'm suggesting, right?
I didn't think so, but maybe I was missing something.
My point is that if we make the exception known to emacsclient, then
when the timeout ends without exceptions, it should be clear it was a
real timeout.
next prev parent reply other threads:[~2023-01-06 18:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 5:47 bug#60592: 30.0.50; emacsclient: exit with a different code when the request times out Sean Whitton
2023-01-06 7:37 ` Eli Zaretskii
2023-01-06 17:57 ` Sean Whitton
2023-01-06 18:12 ` Eli Zaretskii [this message]
2023-01-06 19:03 ` Sean Whitton
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=83zgavttuq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60592@debbugs.gnu.org \
--cc=spwhitton@spwhitton.name \
/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.