From: Juanma Barranquero <lekktu@gmail.com>
To: Wolfgang Schnerring <wosc@wosc.de>
Cc: 6963@debbugs.gnu.org
Subject: bug#6963: More usecases, patch attached
Date: Wed, 29 Sep 2010 16:42:41 +0200 [thread overview]
Message-ID: <AANLkTinBR9-Y3NEbPQMhHrdCbo=ro27sVrVWNp_JwA6D@mail.gmail.com> (raw)
In-Reply-To: <20100929060918.GB9654@elzar.ws.whq.gocept.com>
On Wed, Sep 29, 2010 at 08:09, Wolfgang Schnerring <wosc@wosc.de> wrote:
> But that it does not signal error
> situations via its exit status
It does in most cases.
> since emacsclient returns 0 no matter what.
That's not accurate. When emacsclient detects a problem with itself
(missing server file, error opening socket, etc.) it returns
EXIT_FAILURE (1). What it currently does not do, however, is returning
EXIT_FAILURE for errors passed back from Emacs.
> I've attached a patch that makes emacsclient exit with nonzero status
> when it receives an error message from Emacs -- it already *prints*
> "*ERROR*" in these cases, so I feel this makes a lot of sense.
Yes, it makes sense, because after -error the client's process is
deleted, so emacsclient exits immediately.
So, two questions remain:
- should this be considered a bug, and installed on emacs-23, or a new
feature, for the trunk?
- should emacsclient return 1 for these new errors, or a new error
code (2) to allow distinguishing them?
Juanma
next prev parent reply other threads:[~2010-09-29 14:42 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 [this message]
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
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
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='AANLkTinBR9-Y3NEbPQMhHrdCbo=ro27sVrVWNp_JwA6D@mail.gmail.com' \
--to=lekktu@gmail.com \
--cc=6963@debbugs.gnu.org \
--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 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).