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: Fri, 27 Nov 2009 03:22:51 +0100 [thread overview]
Message-ID: <e01d8a50911261822q6e9d8e2an6d6c8919310ba5c1@mail.gmail.com> (raw)
In-Reply-To: <jwv1vjku4gx.fsf-monnier+emacs@gnu.org>
On Fri, Nov 27, 2009 at 3:09 AM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
>>> So it ends up increasing Emacs's footprint by a bit less than
>>> a megabyte. It's not the end of the world, but it might be worthwhile
>>> trying to avoid loading this data unless it's really needed.
>> The easiest seems to be to split cus-load.el in two part and only load
>> this extra part in C-h v etc.
>
> I think C-h v, C-h f and very common operations which most of the time
> do not need this info, so I'd like to avoid eating up 1MB just for that.
>
>>> Of course, maybe there's a way to represent the same info
>>> more compactly
>> I doubt it is possible, but I do not understand all the figures.
>> Does it help to erase the data again after C-h v?
>
> Erasing the data after use might be a way around the problem.
> Note that in the form in which you currently store the data (Customize
> symbol properties), it's difficult to unload it.
Maybe load this data only when needed and erase them always afterwards.
What is the problem with erasing the data? It is just a simple loop
erasing it all, or?
> If you additionally split the data (e.g. based on the first letter),
> you'd end up only loading a tenth of the data at a time, which would
> seem a lot more reasonable.
Aren't these data only needed in custom operations? Then just
loading/unloading them seems not be operations that will be very
frequent. They are not more frequent than commands if flag them and
erase them at command level. And a 0.1 seconds delay for certain
commands that either load libraries or are meant as information
commands is not very much.
next prev parent reply other threads:[~2009-11-27 2:22 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e01d8a50911261822q6e9d8e2an6d6c8919310ba5c1@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.