Kim F. Storm skrev:
Richard Stallman [EMAIL PROTECTED] writes:
Pre-emption probably doesn't work very well with added latency of an
internet connection, especially given all the buffering. (The Supdup
protocol, which I worked on in 1980 or so, limited the amount of
buffering so that
Jan Djärv [EMAIL PROTECTED] writes:
For the client (Emacs) X buffers all outgoing requests, until you do
an XFlush, XSync or tries to read another XEvent (XNextEvent and such)
or until the output buffer becomes full.
...
That said, your changes seem to have a positive effect on slow
I put the documentation for redisplay-preemption-period next to
redisplay-dont-pause in display.texi -- is there a better place?
Sounds good.
___
emacs-pretest-bug mailing list
emacs-pretest-bug@gnu.org
This could be done by checking for input every 0.10 seconds during
window redisplay (rather than every N lines).
This means that if redisplay is fast enough to complete within 0.10
seconds, it doesn't pre-empt.
That would work, for a terminal, assuming it waits for the output to
Richard Stallman [EMAIL PROTECTED] writes:
I suspect this measurement will be meaningless when using the net,
because it would only tell you how long it took to write all the
output into some buffer in the ethernet driver. You won't even know
when it is sent out on the ethernet.
But then
[EMAIL PROTECTED] (Kim F. Storm) writes:
So please install your patch, and document it. Then we can see
how well it works.
I'll do that.
Done.
I put the documentation for redisplay-preemption-period next to
redisplay-dont-pause in display.texi -- is there a better place?
I also wrote
Richard Stallman [EMAIL PROTECTED] writes:
And how do you decide how fast a remote connection is, nowadays?
Fast! And getting faster!!
That is not always true. I had to use a modem connection twice this
weekend. Even without dialup involved, international connections can
be
What about the Linux console? Of course, we can put something in
term/linux.el, but that will take effect even when going through the
net. Is there a way to distinguish real local use from remote use?
Well, it is the same problem as finding out if a TCP/IP socket is connected
A first step would be to provide more realistic settings for baud_rate
in xterm.c, macterm.c, and w32term.c -- for example, 25 (assuming
that the connection is over a somewhat loaded half-duplex 10 MB LAN).
And then only enable pre-emptive redisplay if baud-rate is 20.
Richard Stallman skrev:
A first step would be to provide more realistic settings for baud_rate
in xterm.c, macterm.c, and w32term.c -- for example, 25 (assuming
that the connection is over a somewhat loaded half-duplex 10 MB LAN).
And then only enable pre-emptive redisplay
10 matches
Mail list logo
