From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org, ")" <kazu@iijlab.net>
Subject: Re: buffering of process output
Date: Mon, 11 Oct 2004 10:37:11 +0200 [thread overview]
Message-ID: <m3r7o5odl4.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <m3hdp242w8.fsf@kfs-l.imdomain.dk> (Kim F. Storm's message of "Mon, 11 Oct 2004 00:36:07 +0200")
no-spam@cua.dk (Kim F. Storm) writes:
> Andreas Schwab <schwab@suse.de> writes:
>
>> storm@cua.dk (Kim F. Storm) writes:
>>
>> It doesn't. It's because there is no call to XFlush during the read loop
>> in call-process. See the comment in xterm.c:
>>
>> /* Remove calls to XFlush by defining XFlush to an empty replacement.
>> Calls to XFlush should be unnecessary because the X output buffer
>> is flushed automatically as needed by calls to XPending,
>> XNextEvent, or XWindowEvent according to the XFlush man page.
>> XTread_socket calls XPending. Removing XFlush improves
>> performance. */
>>
>> Thus redisplay_preserve_echo_area does not call XFlush any more.
>>
>> Andreas.
>
> Thanks for the explanation. I'll fix that.
An explicit flush doesn't fix the problem -- it may have some effect,
but output is still buffered (at least) two lines per update.
I still see cases where the display is not really updated at all
(as if redisplay doesn't see that the display need update).
I'll keep investigating.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
prev parent reply other threads:[~2004-10-11 8:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030716.123727.83083338.kazu@iijlab.net>
2004-10-10 0:08 ` buffering of process output Kim F. Storm
2004-10-10 14:09 ` Andreas Schwab
2004-10-10 22:36 ` Kim F. Storm
2004-10-11 8:37 ` Kim F. Storm [this message]
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=m3r7o5odl4.fsf@kfs-l.imdomain.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=kazu@iijlab.net \
/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.