unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: customize-apropos-options takes forever...
Date: Thu, 6 Jul 2006 10:06:13 -0700	[thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMOEGGCJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <87veqavg3j.fsf@stupidchicken.com>

    >  M-x customize-apropos-options RET RET
    >
    > On Emacs 22, this takes quite a while. On Emacs 20, it finishes very
    > quickly.
    >
    > Emacs 22 has a lot more options, of course, and more faces
    > and buttons and such, but it still feels like things are less
    > efficient now. In emacs -Q, there are 4698 lines in the buffer
    > in Emacs 22; in Emacs 20, there are 2333 lines (about half).
    > But Emacs 22 takes *far* longer than twice as long.

    I took some time to look into this.

Thanks Chong.

    For M-x customize-apropos RET RET:

    Emacs 22 takes 140.04 seconds to make 1904 entries, i.e. 13.6 / second.
    Emacs 21 takes 76.38  seconds to make 1048 entries, i.e. 13.7 / second.

    Conclusion: >>>> This Is Not A Bug <<<<

I was comparing Emacs 20, not Emacs 21. Perhaps the same difference in
performance exists between 20 and 21. Believe me, there is a marked
difference between 20 and 22. Again, I know that Customize in 22 is a lot
fancier than in 20, and it does more behind the scene, so degraded
performance is not a full measure of usefulness - Customize in 22 is better
than in 20, and I don't want to go backward here.

    I think the reason you thought Emacs 22 is slower is that the echo
    area tells you how much % of the job is done.  Obviously, 1% of 1904
    entries takes longer to do than 1% of 1048 entries, giving the
    illusion that Emacs 22 is progressing more slowly.

No, I was not paying attention to the echo area. I was simply waiting for
the buffer to appear (!) and for my keyboard and mouse to come back to me
from Never-Never Land.

    In the reality, of course, it's silly to do M-x customize-apropos with
    no regexp in the first place.

Agreed, but people do silly things sometimes. Searching among all options is
a reasonable thing to want to do, but I agree that there are other ways to
do that.

apropos-variable is good for getting descriptions of all user options (but
not faces) - but it doesn't show you the values. And edit-options is quick
and useful for getting both descriptions and values, but it is deprecated.

  reply	other threads:[~2006-07-06 17:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-05 15:14 customize-apropos-options takes forever Drew Adams
2006-07-05 15:41 ` Chong Yidong
2006-07-06 13:32 ` Richard Stallman
2006-07-06 15:52   ` Drew Adams
2006-07-07 19:30     ` Richard Stallman
2006-07-06 16:43 ` Chong Yidong
2006-07-06 17:06   ` Drew Adams [this message]
2006-07-06 22:55     ` Chong Yidong
2006-07-07 19:31   ` Richard Stallman

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=EIENLHALHGIMHGDOLMIMOEGGCJAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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.
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).