unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: "Sean O'Rourke" <sorourke@cs.ucsd.edu>
Cc: emacs-devel@gnu.org
Subject: Re: remove dabbrev--scanning-message?
Date: Mon, 23 Jul 2007 22:18:30 +0300	[thread overview]
Message-ID: <u4pjvnd2x.fsf@gnu.org> (raw)
In-Reply-To: <m28x97aedn.fsf@cs.ucsd.edu> (sorourke@cs.ucsd.edu)

> From: "Sean O'Rourke" <sorourke@cs.ucsd.edu>
> Date: Sun, 22 Jul 2007 22:16:36 -0700
> 
> When `dabbrev-expand' is invoked with many buffers and it fails
> to find an expansion, there is an annoying forced pause while it
> scans every buffer and emits uninteresting progress messages.  If
> these messages are removed, a failed expansion is nearly
> instantaneous, so I don't see any benefit to having progress
> messages.  Patch attached.

Instead of deleting the functionality altogether, I'd prefer that the
messages could be enabled by customizing some option.  The option
could be off by default (which should be noted in etc/NEWS, btw).

  parent reply	other threads:[~2007-07-23 19:18 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 [this message]
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=u4pjvnd2x.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=sorourke@cs.ucsd.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.
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).