From: Andrea Venturoli <ml.diespammer@netfence.it>
To: help-gnu-emacs@gnu.org
Subject: Re: Why is Emacs so slow when used remotely?
Date: Wed, 22 Sep 2010 21:56:59 GMT [thread overview]
Message-ID: <LYumo.99226$Ua.22677@twister2.libero.it> (raw)
In-Reply-To: <3ebca0e6-c698-44dd-a4fd-6166233f5eba@q26g2000vbn.googlegroups.com>
On 09/21/10 20:29, Russ P. wrote:
> This is disappointing. As far as I can tell, Emacs seems to be
> essentially unusable for remote usage. I can't believe I am the only
> one who has noticed this problem. Am I the only one who uses Emacs/
> XEmacs to work remotely over ssh -X?
I used to use emacs over X/ssh on remote links, but finally had to give
up: with recent versions it has become almost unusable.
Starting it up takes half a minute, it's a bit slow at everything and
you'll have to remember to avoid using certain features: e.g. hitting
Ctrl-K (to delete a line) takes about 10 seconds; same goes for anything
that will (possibly as a side-effect) copy something to the clipboard.
In the end I moved to "emacs -nw" and forgot about X entirely.
Of course, on a LAN, it's a whole different story and I'm using
emacs/X/ssh everyday.
Just my two cents
bye
av.
next prev parent reply other threads:[~2010-09-22 21:56 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-20 23:20 Why is Emacs so slow when used remotely? Russ P.
2010-09-21 1:40 ` despen
2010-09-21 18:29 ` Russ P.
2010-09-21 18:53 ` Thorsten Bonow
2010-09-21 21:19 ` despen
2010-09-21 21:23 ` despen
2010-09-21 22:12 ` Tim X
2010-09-21 22:31 ` Pascal J. Bourguignon
2010-09-22 6:54 ` David Kastrup
2010-09-22 13:05 ` Pascal J. Bourguignon
2010-09-22 13:25 ` David Kastrup
2010-09-22 13:41 ` Pascal J. Bourguignon
2010-09-22 22:33 ` Tim X
2010-09-23 22:50 ` Stefan Monnier
2010-09-21 22:19 ` David Kastrup
2010-09-22 21:56 ` Andrea Venturoli [this message]
2010-09-23 22:54 ` Stefan Monnier
2010-09-24 15:48 ` Giacomo Boffi
2010-09-24 18:01 ` despen
2010-09-23 22:44 ` Stefan Monnier
2010-09-24 2:29 ` despen
2013-11-15 15:47 ` mgrojo
2013-11-15 22:24 ` Bob Proulx
2013-11-15 22:58 ` Drew Adams
2013-11-15 23:30 ` Bob Proulx
2013-11-21 20:13 ` Manuel Gómez
2013-11-21 21:39 ` Bob Proulx
2013-11-27 17:58 ` Ken Goldman
2013-11-27 23:16 ` Peter Dyballa
2013-11-28 2:34 ` Bob Proulx
2013-11-28 11:35 ` Peter Dyballa
2013-11-28 19:48 ` Bob Proulx
2013-11-28 21:53 ` Peter Dyballa
2013-11-29 18:56 ` Bob Proulx
2013-11-30 15:23 ` Perry Smith
2013-11-30 23:03 ` Peter Dyballa
2013-12-01 15:41 ` Perry Smith
2013-11-28 4:11 ` Stefan Monnier
[not found] ` <mailman.6780.1385064830.10748.help-gnu-emacs@gnu.org>
2013-11-24 16:17 ` Kenneth Jacker
2013-11-24 20:02 ` Manuel Gómez
[not found] ` <mailman.6297.1384554313.10748.help-gnu-emacs@gnu.org>
2013-11-16 2:13 ` Dan Espen
2010-09-22 10:44 ` Uday Reddy
[not found] ` <306c0aac-97e2-47b4-bf63-afe247dea2b3@u13g2000vbo.googlegroups.com>
2010-09-23 22:06 ` Tim X
2010-09-24 15:45 ` Giacomo Boffi
2010-09-24 22:32 ` Russ P.
2010-09-25 0:39 ` Tim X
2010-09-27 13:30 ` Giacomo Boffi
2010-09-27 21:11 ` Stefan Monnier
2010-09-27 21:16 ` Giacomo Boffi
2010-09-27 23:01 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2010-09-21 22:32 Russ P.
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='LYumo.99226$Ua.22677@twister2.libero.it' \
--to=ml.diespammer@netfence.it \
--cc=help-gnu-emacs@gnu.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).