unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Emacs-Devel devel <emacs-devel@gnu.org>
Subject: Re: Defcustoms, how do users find them?
Date: Wed, 18 Nov 2009 04:31:25 +0100	[thread overview]
Message-ID: <e01d8a50911171931q2031bc04sb428063f20737274@mail.gmail.com> (raw)
In-Reply-To: <jwvtywsa58d.fsf-monnier+emacs@gnu.org>

On Wed, Nov 18, 2009 at 4:26 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>> I tested this a little. Loading the new cus-load.el now takes about
>> 2.5 times longer time than before. (This is an old pc, it now takes
>> 0.5 sec.) There are approx 15 000 put statements (before there were
>> approx 1000).
>
>> Is this the way to go to get completion etc for unloaded options (and faces)?
>
> I think the basic idea is right, but I think that using `put' for those
> variables is not a good idea (it makes the cus-load.el file large and
> slow).  It's probably preferable to build a single alist associating
> file names to the list of vars defined in them (or maybe a hash-table).
>
> Of course, I haven't tried it, so it may end up being just as slow/big.


Maybe, I just tried to build on what is there. It turns out that after
byte compiling the new cus-load.el loads in 0.1 sec on my quite old
pc.

Are there other aspects that makes it worth investigating this more?
Maybe memory use? I can't see that efficiency in loading could be
affected very much.




  reply	other threads:[~2009-11-18  3:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-16 21:11 Defcustoms, how do users find them? Lennart Borgman
2009-11-16 23:05 ` Stefan Monnier
2009-11-16 23:49   ` Lennart Borgman
2009-11-17  2:52     ` Stefan Monnier
2009-11-17  3:17       ` Lennart Borgman
2009-11-17  3:38         ` Stefan Monnier
2009-11-17  3:41           ` Lennart Borgman
2009-11-17 14:22             ` Lennart Borgman
2009-11-17 14:45               ` Lennart Borgman
2009-11-17 23:13                 ` Lennart Borgman
2009-11-18  3:26                   ` Stefan Monnier
2009-11-18  3:31                     ` Lennart Borgman [this message]
2009-11-18 14:34                       ` Stefan Monnier
2009-11-26 12:51                         ` Lennart Borgman
2009-11-26 16:42                           ` Lennart Borgman
2009-11-26 17:30                             ` Stefan Monnier
2009-11-26 17:36                               ` Lennart Borgman
2009-11-27  2:09                                 ` Stefan Monnier
2009-11-27  2:22                                   ` Lennart Borgman
2009-11-26 16:45                           ` Stefan Monnier
2009-11-17 10:03 ` Juri Linkov
2009-11-17 17:24   ` Glenn Morris
2009-11-18  9:57     ` Juri Linkov
2009-11-18 14:37       ` Stefan Monnier
2009-11-17 17:49   ` Drew Adams
2009-11-17 17:56     ` Lennart Borgman

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=e01d8a50911171931q2031bc04sb428063f20737274@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    /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).