From: "Sean O'Rourke" <sorourke@cs.ucsd.edu>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: emacs-devel@gnu.org
Subject: Re: remove dabbrev--scanning-message?
Date: Mon, 23 Jul 2007 06:40:47 -0700 [thread overview]
Message-ID: <m24pjv9r1c.fsf@cs.ucsd.edu> (raw)
In-Reply-To: <87bqe34isa.fsf@ambire.localdomain> (Thien-Thi Nguyen's message of "Mon\, 23 Jul 2007 10\:37\:57 +0200")
Thien-Thi Nguyen <ttn@gnuvola.org> writes:
> () "Sean O'Rourke" <sorourke@cs.ucsd.edu>
> () Sun, 22 Jul 2007 22:16:36 -0700
>
> so I don't see any benefit to having progress
> messages. Patch attached.
>
> right, so what you want to do is to submit a patch
> that preserves this for those that see the benefit
> while not making you wait, annoyed.
>
> how about replacing the message calls w/ a progress reporter?
I can do this, but progress reporting only makes sense when
there's a noticeable delay. I'm genuinely curious: For those
people on the list with older hardware and/or many open buffers,
with the progress messages removed, does a failed dabbrev-expand
take more than an instant? It didn't for me, with 80 or so
buffers and average hardware.
/s
next prev parent reply other threads:[~2007-07-23 13:40 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 [this message]
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
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=m24pjv9r1c.fsf@cs.ucsd.edu \
--to=sorourke@cs.ucsd.edu \
--cc=emacs-devel@gnu.org \
--cc=ttn@gnuvola.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).