GNU bug report logs - #7989
23.2.91; How do I update "local" autoloads?

Previous Next

Full log

Message #14 received at 7989 <at> debbugs.gnu.org (full text, mbox):

From: Chong Yidong <cyd <at> stupidchicken.com>
To: Reuben Thomas <rrt <at> sc3d.org>
Cc: 7989 <at> debbugs.gnu.org
Subject: Re: bug#7989: 23.2.91; How do I update "local" autoloads?
Date: Tue, 03 May 2011 11:57:19 -0400

> *File M-x update-file-autoloads puts autoloads into.
> A `.el' file can set this in its local variables section to make its
> autoloads go somewhere else.
>
> First, there's something missing here: it doesn't explain that if the
> value is a plain file name, then a directory is automatically
> prepended (and that's the source directory, which seems odd).

I've clarified the docstring, thanks.

> 2. I could set generated-autoload-file before running
> update-directory-autoloads, but I have no idea whether this would have
> a deleterious effect on, for example, ELPA. In a nutshell, why would I
> want to set a global variable for a one-off operation?

ELPA isn't affected, because it explicitly binds generated-autoload-file
to an absolute filename before running update-directory-autoloads.

I agree that the interactive interfaces to update-file-autoloads and
update-directory-autoloads are not very friendly.  Maybe when they are
called interactively, they should prompt for generated-autoload-file.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.