From: Eli Zaretskii <eliz@gnu.org>
To: Craig Muth <craig.muth@gmail.com>
Cc: schwab@suse.de, stephen@xemacs.org, emacs-devel@gnu.org,
mathias.dahl@gmail.com
Subject: Re: Writing to STDOUT from elisp
Date: Wed, 09 Jul 2014 05:48:11 +0300 [thread overview]
Message-ID: <83egxvckno.fsf@gnu.org> (raw)
In-Reply-To: <CAA0bO3E9h3yr=ZHZpWYgUQyQrm11Kk2sMkbSeFpjZF_6P4Phmw@mail.gmail.com>
> Date: Tue, 8 Jul 2014 18:50:23 -0700
> From: Craig Muth <craig.muth@gmail.com>
> Cc: "Stephen J. Turnbull" <stephen@xemacs.org>, Mathias Dahl <mathias.dahl@gmail.com>,
> Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
>
> You can get princ to write to "standard-output", meaning the echo
> area. I'm looking to write to the stdout of the whole process, so the
> output shows up in the terminal you launched emacs in. So when you
> exit emacs, you'll see the text in the shell.
>
> I've asked around and am pretty sure elisp can't do this. I may have
> found the one elemental thing that elisp can't do :)
Please show what did you try and why do you think it didn't do what
you want.
next prev parent reply other threads:[~2014-07-09 2:48 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 [this message]
2014-07-10 2:45 ` Eli Zaretskii
2014-07-10 5:40 ` Craig Muth
2014-07-10 15:03 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83egxvckno.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 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.