From: "Sean O'Rourke" <sorourke@cs.ucsd.edu>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: remove dabbrev--scanning-message?
Date: Mon, 23 Jul 2007 15:58:56 -0700 [thread overview]
Message-ID: <m2veca9173.fsf@cs.ucsd.edu> (raw)
In-Reply-To: <E1ID6Q6-0006NE-UY@fencepost.gnu.org> (Richard Stallman's message of "Mon\, 23 Jul 2007 18\:30\:26 -0400")
Richard Stallman <rms@gnu.org> writes:
> For me, it takes 7 seconds or so with the messages, and 5 seconds with
> no messages. I think I would rather have the messages.
Ouch. For me it's 0.5 or 1 second with messages, and nearly
imperceptible without, making dabbrev-expand convenient for
completing long words while typing text. It sounds like this
feature is almost completely useless to you now.
> Do you have a lot of small buffers?
I currently have 76 buffers taking 7864231 bytes, but about 6M of
that is an enormous *info* buffer, so the median is 3278 bytes.
I'm not sure what people think of as "small".
Given that people do see substantial delays, it seems like the
best approach would be:
(1) Replace the messages with a progress-reporter (assuming
it's faster), since the filenames probably go by too fast to
read anyways.
(2) Provide a user option `dabbrev-report-progress', true by
default, to enable/disable this feedback.
/s
next prev parent reply other threads:[~2007-07-23 22:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 5:16 remove dabbrev--scanning-message? Sean O'Rourke
2007-07-23 8:37 ` Thien-Thi Nguyen
2007-07-23 13:40 ` Sean O'Rourke
2007-07-23 19:19 ` Eli Zaretskii
2007-07-23 19:18 ` Eli Zaretskii
2007-07-24 16:46 ` Richard Stallman
2007-07-24 17:16 ` Sean O'Rourke
2007-07-23 22:30 ` Richard Stallman
2007-07-23 22:58 ` Sean O'Rourke [this message]
2007-07-23 23:18 ` Thien-Thi Nguyen
2007-07-24 0:40 ` Sean O'Rourke
2007-07-24 22:16 ` Richard Stallman
2007-08-22 1:35 ` Thien-Thi Nguyen
2007-08-22 1:49 ` Sean O'Rourke
2007-08-22 21:27 ` Richard Stallman
2007-08-23 9:38 ` Thien-Thi Nguyen
2007-08-22 19:49 ` Thien-Thi Nguyen
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=m2veca9173.fsf@cs.ucsd.edu \
--to=sorourke@cs.ucsd.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).