From: Conrad Lloyd-Knight <clloydknight@rudolphtech.com>
Subject: slow response on first buffer edit
Date: Wed, 20 Oct 2004 14:29:10 -0400 [thread overview]
Message-ID: <20041020182910.GA3180@kelda> (raw)
Hi,
I didn't see this in the FAQ, or in a quick perusal of the archives
for this list...
The problem I'm having is on one particular machine where I have emacs
21.3.1 installed. I have the same version installed on 3 machines and
this is the only one showing this.
The first edit of a buffer causes a high CPU load for about 10s before
any changes show up in the window. This occurs when emacs is started
with:
emacs filename
but not when started with just:
emacs
(in other words, the effect doesn't show up when editing the scratch
buffer). It occurs whether filename is an existing file or a new one.
I can move around the buffer using the cursor keys, etc. but the
moment I make a change to what is displayed (kill a line, type a
character...) the system appears to hang for 10s before the change is
displayed.
I have also noticed that this hangup occurs before a symbolic link is
created, by the name of .#filename, pointing to a non-existant file
called user@full.hostname.PID:somelongnumber. I do not believe the
delay is caused by creating this link, as I can manually create a
similarly named one without any delay, but this might give someone an
idea at what point it occurs.
Another data point: I can open a second file in another buffer and
edit this afterwards without another delay.
This issue has me stumped, so if anyone else has seen this, I'd
appreciate any insight. Or if anyone has any suggestions on how to
diagnose this further, please let me know! :)
Thanks,
-C.
next reply other threads:[~2004-10-20 18:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-20 18:29 Conrad Lloyd-Knight [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 18:04 slow response on first buffer edit Conrad Lloyd-Knight
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=20041020182910.GA3180@kelda \
--to=clloydknight@rudolphtech.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).