Re: Strange delays when running remotely
On Mon, 01 Jul 2002, sigeti(a)lanl.gov wrote:
Dear Jeff,
At 06:11 PM 7/1/2002 -0400, Jeff Mincy wrote:
>On 02 Jul 2002, ville.skytta(a)xemacs.org wrote:
>
> > On Mon, 2002-07-01 at 23:57, David E. Sigeti wrote:
> >
> >> Dear Bug Team!
> >>
> >> When running Xemacs version 21 remotely (displaying on my local X
> >> server) I have found that any multicharacter kills (such as kill-line,
> >> kill-word, kill-ring-save, etc.) are extremely slow (maybe 15-30
> >> seconds per kill). I only see this delay when I am running over a DSL
> >> connection where the ping times to the remote system are on the order
> >> of 100 milliseconds or more. ...
>Try setting interprogram-cut-function and
interprogram-paste-function
>to nil.
Thanks for a much for the suggestion. I will try it when I get home this
evening. I assume that setting these hooks to nil will make it impossible
to cut and paste between Xemacs and other applications. I don't cut and
paste between Xemacs and other applications very often, but when I do I
really want the capability. I suppose that I can restore the cut and paste
capability (at the price of terrible performance when killing) by resetting
the hooks to the default values. Does this sound reasonable?
First lets worry about whether this fixes your problem, but,
no - setting the variables to nil only prevents the usual kill-line (etc)
changes from going into the clipboard. You can still use functions
that copy to the clipboard. I use toolbar-copy-function on my remote
xemacs for doing this, which for me has 20ms ping times.
Although now that you mention it, I wonder what the clipboard
functions are doing that takes so long when running remotely.
I tried looking at the code briefly, but I got lost in select.c.
Version 20 of Xemacs allowed cutting and pasting without suffering
from
terrible performance when killing. Is this problem just a bug that we can
expect to be fixed in a later version, or is there something fundamental
about the way cutting and pasting are being done now that makes performance
terrible on connections with high latencies?
I think the default values of these particular variables were changed
in ~21.4.4.
Yours,
David
-jeff