From: Eli Zaretskii <eliz@gnu.org>
To: Craig Muth <craig.muth@gmail.com>
Cc: schwab@suse.de, stephen@xemacs.org, mathias.dahl@gmail.com,
emacs-devel@gnu.org
Subject: Re: Writing to STDOUT from elisp
Date: Thu, 10 Jul 2014 18:03:53 +0300 [thread overview]
Message-ID: <83vbr5b6hy.fsf@gnu.org> (raw)
In-Reply-To: <CAA0bO3GHu8JwTBnZzSBHJ5OqXA9GbS9+v7n8kyiZyxJbb_aEyw@mail.gmail.com>
> Date: Wed, 9 Jul 2014 22:40:09 -0700
> From: Craig Muth <craig.muth@gmail.com>
> Cc: Andreas Schwab <schwab@suse.de>, "Stephen J. Turnbull" <stephen@xemacs.org>, emacs-devel@gnu.org,
> Mathias Dahl <mathias.dahl@gmail.com>
>
> > If you want to do this in an interactive session
>
> Yes, in an interactive session.
>
> > please tell what
> > exactly are you trying to do and why. For example, is this only
> > needed when you exit Emacs
>
> Doing it when exiting emacs would work.
Then one way of doing this is call kill-emacs with a non-nil argument,
then wrap Emacs in a shell script that would do whatever you want
depending on the Emacs exit code.
Of course, submitting (trivial) patches for adding a command to write
to stdout would probably be welcome as well. But please note that
sometimes Emacs is invoked with stdout redirected to some obscure
file, or even with stdout being closed/invalid.
next prev parent reply other threads:[~2014-07-10 15:03 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-28 22:51 Writing to STDOUT from elisp Craig Muth
2014-07-08 6:36 ` Mathias Dahl
2014-07-08 7:03 ` Stephen J. Turnbull
2014-07-08 14:54 ` Eli Zaretskii
2014-07-08 15:38 ` Andreas Schwab
2014-07-08 17:02 ` Stephen J. Turnbull
2014-07-08 18:59 ` Andreas Schwab
2014-07-09 1:50 ` Craig Muth
2014-07-09 2:48 ` Eli Zaretskii
2014-07-10 2:45 ` Eli Zaretskii
2014-07-10 5:40 ` Craig Muth
2014-07-10 15:03 ` Eli Zaretskii [this message]
2014-07-10 15:20 ` Lennart Borgman
2014-07-10 18:01 ` Craig Muth
2014-07-11 12:04 ` Thien-Thi Nguyen
2014-07-10 19:09 ` Johan Bockgård
2014-07-10 19:25 ` Eli Zaretskii
2014-07-10 22:54 ` Johan Bockgård
2014-07-09 3:55 ` Stephen J. Turnbull
2014-07-09 7:24 ` Andreas Schwab
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=83vbr5b6hy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=craig.muth@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=mathias.dahl@gmail.com \
--cc=schwab@suse.de \
--cc=stephen@xemacs.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.
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).