From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 8858@debbugs.gnu.org, "Eric M. Ludlam" <zappo@gnu.org>
Subject: bug#8858: 24.0.50; duplicate defaliases in eieio.el and eieio-opt.el
Date: Fri, 01 Jul 2011 16:17:04 +0200 [thread overview]
Message-ID: <m3y60ikrvj.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <362319DAB6B74309882EB813870D3471@us.oracle.com> (Drew Adams's message of "Mon, 13 Jun 2011 15:31:34 -0700")
"Drew Adams" <drew.adams@oracle.com> writes:
> I know nothing about eieio. I have no idea whether this is actually a
> bug, but it seemed odd. There are duplicate defaliases in these two
> files. Should there be? HTH.
The autoloads are apparently automatically extracted from the other
files, and put into eieio.el. This seems unnecessary, since Emacs itself
will extract the autoloads.
Example:
;;;### (autoloads (eieio-help-mode-augmentation-maybee eieio-describe-generic
;;;;;; eieio-describe-constructor eieio-describe-class eieio-browse)
;;;;;; "eieio-opt" "eieio-opt.el" "1bed0a56310f402683419139ebc18d7f")
;;; Generated autoloads from eieio-opt.el
(autoload 'eieio-browse "eieio-opt" "\
Create an object browser window to show all objects.
If optional ROOT-CLASS, then start with that, otherwise start with
variable `eieio-default-superclass'.
\(fn &optional ROOT-CLASS)" t nil)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-07-01 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-13 22:31 bug#8858: 24.0.50; duplicate defaliases in eieio.el and eieio-opt.el Drew Adams
2011-07-01 14:17 ` Lars Magne Ingebrigtsen [this message]
2011-07-01 16:50 ` Andreas Schwab
2011-07-01 16:59 ` Lars Magne Ingebrigtsen
2011-07-01 21:10 ` Glenn Morris
2011-07-02 12:30 ` Lars Magne Ingebrigtsen
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=m3y60ikrvj.fsf@quimbies.gnus.org \
--to=larsi@gnus.org \
--cc=8858@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=zappo@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 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).