Re: Why is Emacs so slow when used remotely?

[Tim X <timx@nospam.dev.null>]

pjb@informatimago.com (Pascal J. Bourguignon) writes:

> David Kastrup <dak@gnu.org> writes:
>
>> pjb@informatimago.com (Pascal J. Bourguignon) writes:
>>
>>> Tim X <timx@nospam.dev.null> writes:
>>>
>>>> A few things to try ...
>>>>
>>>> 1. turn off tooltip mode
>>>
>>> Yes. Anything graphic.
>>>
>>>
>>>> 2. Try running with -nw to turn off X and only have a terminal UI
>>>> and see what the performance is like. this will let you know if
>>>> the problem is basic emacs or the X protocol stuff
>>>
>>> This is not useful, if you only work with text.  The X protocol is
>>> not significantly worse than any other terminal protocol to send
>>> over text.
>>

Not my practical experience. When I run I don't use the menus, mouse or
toolbar. However, -nw is much faster than X. The only issue I've had is
with different local X terminals 'grabbing' some keys, making some key
combinations harder to achieve in the remote emacs. Depending on yhour
window manager and terminal emulator, it may be necessary to tweak
things to get the full list of keys to the remote emacs.

However, my recommendation for the OPs question is to run one of the X
compression protocols. X was designed for a LAN rather than a WAN and
has a lot of overhead. However, much of this is easily compressed. 

In the past, on a 56k modem, I used dxcp with good results. Still a bit
slow, but usable. Anyone using DSL should get much better results. 

There is also nxproxy, which I've not used, but which is based on the
concepts in dxcp. 

Setting up dxcp was fairly trivial. 

Tim

-- 
tcross (at) rapttech dot com dot au