From: Andreas Politz <politza@hochschule-trier.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Weird behavior of kill-emacs
Date: Wed, 18 Feb 2015 21:07:05 +0100 [thread overview]
Message-ID: <874mqj0ys6.fsf@hochschule-trier.de> (raw)
In-Reply-To: <83y4nv3u6h.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 18 Feb 2015 21:18:14 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
>> Is there a way to work around this behavior?
>
> Why would you want to?
emacs < /dev/null -Q --batch --eval '(progn (ignore-errors (read)) (kill-emacs 42))'; echo $?
returns with exit code 0, i.e. the argument to kill-emacs is ignored. I
guess the OP reads from stdin until EOF, which implies a fixed exit code
of 0.
-ap
next prev parent reply other threads:[~2015-02-18 20:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-18 18:58 Weird behavior of kill-emacs Philipp Stephani
2015-02-18 19:18 ` Eli Zaretskii
2015-02-18 20:07 ` Andreas Politz [this message]
2015-02-18 20:49 ` Philipp Stephani
2015-02-18 20:44 ` Philipp Stephani
2015-02-18 21:02 ` Andreas Politz
2015-02-18 19:25 ` Eli Zaretskii
2015-02-18 21:04 ` Philipp Stephani
2015-02-18 21:17 ` 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=874mqj0ys6.fsf@hochschule-trier.de \
--to=politza@hochschule-trier.de \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@gnu.org \
/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.
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).