From: Krishnakumar B <kitty@cs.wustl.edu>
Subject: Re: remote X11/GNU emacs/ssh: Incredible slowness loading libs
Date: 30 Sep 2002 18:08:07 -0500 [thread overview]
Message-ID: <dmlit0njctk.fsf@samba.doc.wustl.edu> (raw)
In-Reply-To: anaj0j$bre$1@bob.news.rcn.net
On Monday, 30 September 2002, "David Abrahams" wrote:
>
> No need to get nasty. It's hard to know what information people will find
> relevant.
Sorry if I sounded rude. Running an X application on a non-native X server
like Exceed always has problems related to fonts.
> > I have also had slowdowns with running Emacs 21 when X is enabled. This
> > happens when I try connecting to the remote machine using rxvt (shipped
> > with Cygwin).
>
> I'm not using rxvt, to my knowledge.
What terminal are you using ?
> > Try switching your SSH client (for example use PUTTY's terminal
> > window).
>
> Do you really think that's the culprit, considering that I have no
> problems with "emacs -nw" run in an xterm window?
Since I have exact symptoms that you posted and it works for me when I do
this, I suggested this. It's up to you.
> I also have no problems running emacs over ssh outside X11, in a regular
> cygwin window.
What does "outside" mean ?
> > I don't know what is causing the slowdowns in the case when I login
> > using plink -ssh <hostname>
>
> plink?
It's the command-line utility that ships with Putty.
> > and then start Emacs as to using a separate terminal window. Maybe
> > something to do with tty initialization. FWIW, I tried using the
> > Windows command shell and it works like a charm.
>
> The windows command shell always works, but usually not like a charm. What
> were you using it for?
To login to a remote machine and start Emacs on the remote machine and have
it display using an X server running on the local windows machine.
> > > 2. Wouldn't know how to use it if I could find it
> > > 3. Wouldn't know how to interpret the results
> >
> > tcpdump is too much for this unless you want to get to the root of the
> > problem.
>
> I wouldn't mind, if it resulted in a useful bug report to the GNU emacs
> developers.
Again it's up to you. If you have the time, I am sure that the GNU Emacs
developers will appreciate the extra information.
-kitty.
next prev parent reply other threads:[~2002-09-30 23:08 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-29 16:26 remote X11/GNU emacs/ssh: Incredible slowness loading libs David Abrahams
2002-09-29 20:21 ` Kai Großjohann
2002-09-29 20:52 ` David Abrahams
2002-09-29 23:00 ` Edward O'Connor
2002-09-29 23:31 ` David Abrahams
2002-09-30 9:11 ` David Kastrup
2002-09-30 12:04 ` David Abrahams
2002-09-30 12:48 ` David Kastrup
2002-09-30 13:52 ` David Abrahams
2002-09-30 19:10 ` Thomas F. Burdick
2002-09-30 20:14 ` David Abrahams
2002-10-01 7:31 ` Tim Cross
2002-10-01 10:42 ` David Abrahams
2002-10-01 11:36 ` David Kastrup
2002-10-01 12:15 ` David Abrahams
2002-10-02 7:42 ` Matthew Kennedy
2002-09-30 15:04 ` Heinz Rommerskirchen
2002-09-30 14:28 ` Kai Großjohann
2002-09-30 18:34 ` David Abrahams
2002-09-30 21:58 ` Krishnakumar B
2002-09-30 21:46 ` David Abrahams
2002-09-30 23:08 ` Krishnakumar B [this message]
2002-09-30 23:40 ` David Abrahams
2002-10-01 0:40 ` Christopher Browne
2002-10-01 0:13 ` David Abrahams
2002-10-01 2:28 ` Krishnakumar B
2002-10-01 2:57 ` David Abrahams
2002-10-01 15:06 ` Richard V. Molen
2002-10-01 15:25 ` David Abrahams
2002-10-01 16:59 ` Richard V. Molen
2002-10-01 16:43 ` David Abrahams
2002-10-01 18:10 ` Richard V. Molen
2002-09-29 21:26 ` Krishnakumar B
2002-09-29 22:16 ` David Abrahams
2002-10-03 18:30 ` frobware inc
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=dmlit0njctk.fsf@samba.doc.wustl.edu \
--to=kitty@cs.wustl.edu \
/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).