Re: [PATCH] [packages] Move filename and interpreter associations to packages
Ville Skyttä <scop(a)xemacs.org> wrote:
> That is the workaround I intended to have in CC Mode. Why
can't it be
> used?
It can, but doing that in CC Mode doesn't help the N other packages out
there. I'm looking for a solution that would need to be done once, and
which would work for all of them.
Ok, I just wanted to be sure about the reason. Note that I approach
this from the perspective of an independent package maintainer, not an
XEmacs maintainer.
/.../ autoloads in packages are *not* copied to loaddefs.el, but
into a package-specific auto-autoloads.el. And autoloads in
packages have nothing to do with building XEmacs.
Ok, but the end result approximately the same from the package point
of view, i.e. that the form after the ;;;###autoload cookie is
executed at XEmacs startup or some other time before the rest of the
package is loaded?
If so, my question essentially remains: Is there some situation where
the autoloads (wherever they might be stored) in older XEmacsen are
updated with newer packages?
/.../ Autoloads generated from packages stay in packages and are
installed with them. And modes in packages don't "exist in" any
XEmacsen (>= 21.1). That's why it makes no sense to have a central
auto-mode-alist in core containing entries for modes that don't
necessarily exist.
That's very neat.
Given this, I don't see a reason why doing just a
;;;###autoload (add-to-list 'auto-mode-alist '("\\.m\\'" .
objc-mode))
...wouldn't solve the problem (ie. the only change to the current
situation being that the list wouldn't be updated on mode load time).
It would be enough in XEmacs >= 21.1 when the user installs CC Mode
via the XEmacs package system, but I have to make sure things work
nicely also in older XEmacs versions, and in FSF Emacs, and when the
CC Mode dist tarball is downloaded directly from my website.