unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Lennart Borgman'" <lennart.borgman@gmail.com>,
	"'Alan Mackenzie'" <acm@muc.de>
Cc: 5529@debbugs.gnu.org
Subject: bug#5529: `uniquify-buffer-name-style' doesn't exist
Date: Sat, 6 Feb 2010 10:37:24 -0800	[thread overview]
Message-ID: <2A67ED58EE6049D085C4F7413DC8DF74@us.oracle.com> (raw)
In-Reply-To: <e01d8a51002061018n31bc98a4lb8bbf06d90f71f4@mail.gmail.com>

> We can autoload defcustoms, but there are so many so we probably do
> not want that. There are about 7000 and autoloading them all will take
> some computer resources.

How many resources? Just what is involved?

The point of autoload is to load just a pointer to a target, rather than loading
the target itself. Why would 7000 additional autoloads be a big runtime or
load-time burden?

I'm not claiming it is not a big burden. I'm asking why it is. I don't see why
it would be so costly for Emacs to record 7000 vars and their target files for
loading.

I haven't seen any explanation or cost analysis so far. All I've seen is Stefan
screaming, essentially, "NO! DON'T!!!". I'm not saying he's wrong. But what's
wrong with seeing some analysis of the cost involved?







  reply	other threads:[~2010-02-06 18:37 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-05 15:18 bug#5529: `uniquify-buffer-name-style' doesn't exist Alan Mackenzie
2010-02-05 15:56 ` Lennart Borgman
2010-02-05 18:17   ` Alan Mackenzie
2010-02-05 18:18     ` Lennart Borgman
2010-02-06 18:17       ` Alan Mackenzie
2010-02-06 18:18         ` Lennart Borgman
2010-02-06 18:37           ` Drew Adams [this message]
2010-02-06 20:44           ` Alan Mackenzie
2010-02-08  1:49             ` Stefan Monnier
2010-02-05 20:10     ` Stefan Monnier
2010-02-05 17:06 ` Glenn Morris
2010-02-05 20:01   ` Alan Mackenzie
2010-02-08  7:23 ` Glenn Morris

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=2A67ED58EE6049D085C4F7413DC8DF74@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=5529@debbugs.gnu.org \
    --cc=acm@muc.de \
    --cc=lennart.borgman@gmail.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).