From: Chong Yidong <cyd@stupidchicken.com>
To: Juanma Barranquero <lekktu@gmail.com>
Cc: 6963@debbugs.gnu.org, Wolfgang Schnerring <wosc@wosc.de>
Subject: bug#6963: More usecases, patch attached
Date: Sat, 02 Oct 2010 20:00:52 -0400 [thread overview]
Message-ID: <87r5g8i1qj.fsf@stupidchicken.com> (raw)
In-Reply-To: <AANLkTin66P=jHH-wttxi2KcjChH9Fd3gv2YFPqCTDiB7@mail.gmail.com> (Juanma Barranquero's message of "Thu, 30 Sep 2010 03:52:22 +0200")
Juanma Barranquero <lekktu@gmail.com> writes:
> 1) The emacs server sends -error XXX, and closes the connection.
> emacsclient prints the error and exits.
> 2) The emacs server sends an unknown command; emacsclient prints an
> error and continues.
>
> With your patch, the case 2) would return EXIT_FAILURE (or the new
> exit code we discussed) even if subsequent commands are dealt with
> correctly.
>
> IIRC, receiving an unknown command from Emacs shouldn't be a fatal
> error; it can happen if you use an older emacsclient to connect to a
> more recent server.el with new functionality. Or should it?
I agree, the second case should not lead to EXIT_FAILURE. I've checked
the patch, with this and a couple of other corrections, into the trunk.
next prev parent reply other threads:[~2010-10-03 0:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 10:16 bug#6963: 23.2; emacsclient -e "(remember-other-frame)" doesn’t give an error-code on error Arne Babenhauserheide
2010-09-29 6:09 ` bug#6963: More usecases, patch attached Wolfgang Schnerring
2010-09-29 7:02 ` Thierry Volpiatto
2010-09-29 14:42 ` Juanma Barranquero
2010-09-29 15:08 ` Wolfgang Schnerring
2010-09-29 15:43 ` Juanma Barranquero
2010-09-29 18:01 ` Wolfgang Schnerring
2010-09-30 1:52 ` Juanma Barranquero
2010-10-03 0:00 ` Chong Yidong [this message]
2010-10-03 0:38 ` Juanma Barranquero
2010-10-03 4:55 ` Chong Yidong
2010-10-03 10:44 ` Juanma Barranquero
2010-10-22 21:23 ` bug#6963: Thank you! Arne Babenhauserheide
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=87r5g8i1qj.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=6963@debbugs.gnu.org \
--cc=lekktu@gmail.com \
--cc=wosc@wosc.de \
/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.