[PATCH] Raw strings, from Python via SXEmacs

[Jerry James]

Aidan Kehoe <kehoea at parhasard.net> wrote:
>  Ar an t-ochtú lá déag de mí Iúil, scríobh Stephen J. Turnbull: 
>
>  > I would guess it's in the lstream code, which Jerry and Tony Bennett
>  > have been playing with over the last year or so.  I suspect their
>  > patches are responsible for the "Write failed flushing stdout
>  > buffer.\nwrite stdout: broken pipe" warnings I've been seeing using
>  > CVS recently.

Really?  As far as I know, this is the only nontrivial change I made to
the lstream code:

2004-11-12  Jerry James  <james at xemacs.org>

        * lstream.c (Lstream_really_write): Don't call the flusher if the
        writer returned an error.

I remember talking with Tony about a bug he was chasing, but I can't
seem to find a corresponding ChangeLog entry, nor does "cvs log" show
anything I can identify as originating with Tony.

> I reported it first just over two years ago;
> http://mid.gmane.org/20040708204208.316043280C3@ns5.nestdesign.com . I
> suspect it was introduced when Ben made console-coding-streams work
> properly, which was a year at least before that. Unfortunately, I don't have
> a Linux desktop machine to hand, I can't provoke it on NetBSD, OS X or
> Cygwin, and I'm a little reluctant to put my friend's server under stress by
> developing on it :-( .

I can provoke it at will.  Back home I stick with X Windows.  So it's
lucky that I'm logging in to my office machine remotely over a TTY this
summer.

The fact that it only manifests on Linux suggests that it is a Linux
bug, but I'll see if I can track it down.  It's been bothering me, too.
-- 
Jerry James, Assistant Professor        james at xemacs.org
Computer Science Department             http://www.cs.usu.edu/~jerry/
Utah State University