Re: Adding streams for standard out and standard err

[phillip.lord@russet.org.uk (Phillip Lord)]

Phil Sainty <psainty@orcon.net.nz> writes:

> I'm all for a more obvious way to write to stderr (albeit more for
> batch uses in my case).
>
> In http://debbugs.gnu.org/cgi/bugreport.cgi?bug=17390 it was pointed
> out to me that a PRINTCHARFUN function for stderr already exists --
> `external-debugging-output' defined in print.c
>
> I failed to follow up on that, but at the time I was thinking that
> it would be nice to have a `standard-error' variable set to this
> function, just like there's a `standard-output' variable, as it
> would be dramatically more discoverable that way.
>
> As `external-debugging-output' hadn't already cropped up in this
> discussion, I just wanted to point it out in case it wasn't known
> to everyone.


Well, there you go, never knew about that. And, except for the name, and
the fact that it gets whitespace correct, it's identical to my stderr.

I think my name is better, but open to differences of opinion.

So, options:

1) drop my patch
2) accept my patch, make external-debbugging-output use stderr (or vice
versa), to keep the name alive.

Don't really mind. I have no use case that differentiates between stderr
and stdout.

Phil