unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "David Abrahams" <david.abrahams@rcn.com>
Subject: remote X11/GNU emacs/ssh: Incredible slowness loading libs
Date: Sun, 29 Sep 2002 12:26:25 -0400	[thread overview]
Message-ID: <an7bj5$g4u$1@bob.news.rcn.net> (raw)

I've been doing some work on remote machines on the other U.S. coast
recently, and have noticed strange and horrible delays associated with
running GNU emacs in an X window. At first I thought the problem was the
speed of traffic associated with X11, but I don't think so any more. The
reason I say these delays are strange is that they seem to be worst when
emacs is loading libraries (especially during startup), or just when it's
trying to respond to "C-x C-f" the first time. On some machines, it takes
literally minutes to give me the "find file:" prompt. I don't see the same
problems when running "emacs -nw" in an xterm (that just blasts along like
crazy), so it can't be having trouble loading the libraries. I don't see
anything this bad when running Xemacs, so I doubt there's a real problem
with the X11 GUI stuff. Can't imagine what the problem is. Any ideas?

TIA,
Dave Abrahams

--
-----------------------------------------------------------
           David Abrahams * Boost Consulting
dave@boost-consulting.com * http://www.boost-consulting.com

             reply	other threads:[~2002-09-29 16:26 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-29 16:26 David Abrahams [this message]
2002-09-29 20:21 ` remote X11/GNU emacs/ssh: Incredible slowness loading libs 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
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='an7bj5$g4u$1@bob.news.rcn.net' \
    --to=david.abrahams@rcn.com \
    /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).