unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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: Sun, 03 Oct 2010 00:55:40 -0400	[thread overview]
Message-ID: <87r5g727ub.fsf@stupidchicken.com> (raw)
In-Reply-To: <AANLkTiksEHEc3QhngCOWU+ojP4cDTeFHzsk6LrhFhLDS@mail.gmail.com> (Juanma Barranquero's message of "Sun, 3 Oct 2010 02:38:29 +0200")

Juanma Barranquero <lekktu@gmail.com> writes:

> On Sun, Oct 3, 2010 at 02:00, Chong Yidong <cyd@stupidchicken.com> wrote:
>
>> 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.
>
> OK, though I agree with Wolfgang that the first case would be more
> useful returning a new EXIT_EMACSERROR (2) instead of EXIT_FAILURE
> (1).

I'm ambivalent.  This argument implies that we should give different
exit code for everything that could lead to failure in emacsclient, and
there are 18 separate cases in emacsclient.c.  It seems to me that, in
practice, people don't bother looking up the exit code, since there's no
established convention (other than 0 for success and 1 for failure);
they just look at the error message.





  reply	other threads:[~2010-10-03  4:55 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
2010-10-03  0:38         ` Juanma Barranquero
2010-10-03  4:55           ` Chong Yidong [this message]
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=87r5g727ub.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 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).