From: phillip.lord@russet.org.uk (Phillip Lord)
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Adding streams for standard out and standard err
Date: Thu, 21 Jul 2016 19:52:58 +0100 [thread overview]
Message-ID: <87k2ge3jsl.fsf@russet.org.uk> (raw)
In-Reply-To: <83eg6nysug.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 21 Jul 2016 17:21:43 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: phillip.lord@russet.org.uk (Phillip Lord)
>> Date: Wed, 20 Jul 2016 23:48:43 +0100
>>
>> For a while I've wanted Emacs to have the ability to write to standard
>> out, and/or standard err, when not running in batch. Mostly, I've wanted
>> for debugging, as it involves touching no buffers at all.
>
> Can we take a step back and talk about the need and the use cases?
Mostly debugging, I think. For example, I find debugging the undo code
very taxing. Using GDB is hard because the debug code gets called so
often (I admit to being barely competent at using GDB). Logging to a
buffer touches other buffers. Logging to a variable works, but you can
only see the value of the variable when all is done.
Dumping to stdout, while interacting with a live emacs would give me an
independent channel to getting output, as well as post-hoc debugging.
> Here're some thoughts related to this:
>
> . We already have (append-to-file START END FILENAME), which can be
> used to write a buffer or a string to a file. FILENAME can be
> "/dev/stderr" on Posix platforms, for example, or it can be a real
> file name.
We do, and I am grateful that you pointed this out to me. But
append-to-file also writes to the mini-buffer. This makes interactive
use difficult, or painful. Of course, this could be fixed.
Still,
(append-to-file (print buffer-undo-list) nil "/dev/stderr")
seems clunky compared to:
(print buffer-undo-list 'stdout)
> . On TTY frames, writing to standard streams can end up on the
> screen, in which case it will mess up the display.
Yep. I would imagine that debugging to standard out will not become
popular as a tool for debugging TTY display.
> . On GUI frames, writing to standard streams can end up in some
> unpredictable place on the system, or even in the bitbucket,
> depending on what window system, desktop, and window manager are
> installed. On some systems, standard streams have invalid file
> descriptors in GUI sessions.
It can also end up in some entirely predictable place, which is enough.
> So this proposed functionality sounds (a) not really necessary, and
> (b) somewhat unreliable/dangerous. If you have specific use cases
> where the existing functionality doesn't fit the bill, and the issues
> mentioned above are non-issues, please describe those use cases.
I think it has no problems that append-to-file does not not have, and is
neater, more concise and it's use is clearer.
Probably adding a stdin stream would be good also; still, that's a
separate issue.
Phil
next prev parent reply other threads:[~2016-07-21 18:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 22:48 Adding streams for standard out and standard err Phillip Lord
2016-07-21 7:12 ` Andreas Schwab
2016-07-21 18:42 ` Phillip Lord
2016-07-25 7:35 ` Andreas Schwab
2016-07-21 14:21 ` Eli Zaretskii
2016-07-21 14:40 ` Paul Eggert
2016-07-21 15:02 ` Eli Zaretskii
2016-07-21 19:01 ` Phillip Lord
2016-07-21 18:52 ` Phillip Lord [this message]
2016-07-21 19:11 ` Eli Zaretskii
2016-07-21 20:13 ` Phillip Lord
2016-07-22 6:50 ` Eli Zaretskii
2016-07-22 15:43 ` Phillip Lord
2016-07-21 22:15 ` Davis Herring
2016-08-02 23:35 ` John Wiegley
2016-07-22 14:48 ` Phil Sainty
2016-07-22 15:42 ` Phillip Lord
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=87k2ge3jsl.fsf@russet.org.uk \
--to=phillip.lord@russet.org.uk \
--cc=eliz@gnu.org \
--cc=emacs-devel@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.
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.