From: Noam Postavsky <npostavs@users.sourceforge.net>
To: 29471@debbugs.gnu.org
Subject: bug#29471: 26.0.90; [PATCH] Let autoload-compute-prefix be set file-locally
Date: Mon, 27 Nov 2017 07:45:23 -0500 [thread overview]
Message-ID: <877eubopp8.fsf@users.sourceforge.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 158 bytes --]
Tags: patch
Severity: minor
Motivating example is elpa/packages/yasnippet/yasnippet-debug.el for
which it doesn't make sense to register autoload prefixes.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: patch --]
[-- Type: text/x-diff, Size: 981 bytes --]
From a1c9f1768463f44e155b963bd8af26ea29e7dcfb Mon Sep 17 00:00:00 2001
From: Noam Postavsky <npostavs@gmail.com>
Date: Mon, 27 Nov 2017 07:26:10 -0500
Subject: [PATCH] Let autoload-compute-prefix be set file-locally
* lisp/emacs-lisp/autoload.el (autoload-compute-prefixes): Mark
boolean values as safe.
---
lisp/emacs-lisp/autoload.el | 1 +
1 file changed, 1 insertion(+)
diff --git a/lisp/emacs-lisp/autoload.el b/lisp/emacs-lisp/autoload.el
index 27426c4530..a18e7fa4a9 100644
--- a/lisp/emacs-lisp/autoload.el
+++ b/lisp/emacs-lisp/autoload.el
@@ -497,6 +497,7 @@ autoload-compute-prefixes
Standard prefixes won't be registered anyway. I.e. if a file \"foo.el\" defines
variables or functions that use \"foo-\" as prefix, that will not be registered.
But all other prefixes will be included.")
+(put 'autoload-compute-prefixes 'safe #'booleanp)
(defconst autoload-def-prefixes-max-entries 5
"Target length of the list of definition prefixes per file.
--
2.11.0
next reply other threads:[~2017-11-27 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 12:45 Noam Postavsky [this message]
2017-12-02 14:55 ` bug#29471: 26.0.90; [PATCH] Let autoload-compute-prefix be set file-locally Noam Postavsky
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=877eubopp8.fsf@users.sourceforge.net \
--to=npostavs@users.sourceforge.net \
--cc=29471@debbugs.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).