From: David Engster <deng@randomsample.de>
To: help-gnu-emacs@gnu.org
Subject: Re: eieio persistent, plus autoloads
Date: Sat, 17 Aug 2013 09:21:54 +0200 [thread overview]
Message-ID: <874naopyst.fsf@arcor.de> (raw)
In-Reply-To: 87haepez2c.fsf@ericabrahamsen.net
Eric Abrahamsen writes:
> Okay, I guess I get it. I was thinking of eieio-persistent as a slightly
> unusual case just because object constructors are being written to a
> file, and the potential for breakage seems a little more dramatic. But
> perhaps some nice error handling and reporting is all that's necessary.
`eieio-defclass-autoload' only creates a mock class; this is necessary
so that EIEIO already knows about it, but that class is not yet
functional. It then creates a plain `autoload' for the actual
constructor function. So far this has worked very well, at least for
CEDET, which autoloads a lot of classes.
> Just out of curiosity, how do you create an autoload file for your
> smaller packages?
With an emacs script like this:
#!emacs --script
(setq my-base-path (expand-file-name "~/emacs-packages/"))
(setq dirs '("smallstuff" "speck" "minimap" "magit"))
(let ((generated-autoload-file (concat my-base-path "loaddefs.el")))
(cd my-base-path)
(dolist (dir dirs)
(update-directory-autoloads dir)))
-David
next prev parent reply other threads:[~2013-08-17 7:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-15 10:45 eieio persistent, plus autoloads Eric Abrahamsen
2013-08-15 16:05 ` David Engster
2013-08-16 2:03 ` Eric Abrahamsen
2013-08-16 15:18 ` David Engster
2013-08-17 4:11 ` Eric Abrahamsen
2013-08-17 7:21 ` David Engster [this message]
2013-08-19 2:18 ` Eric Abrahamsen
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=874naopyst.fsf@arcor.de \
--to=deng@randomsample.de \
--cc=help-gnu-emacs@gnu.org \
/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.