From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: mvoteiza@udel.edu, 28607@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#28607: 27.0.50; help-fns unsolicited elisp loading
Date: Mon, 20 May 2019 13:49:34 -0400 [thread overview]
Message-ID: <875zq5audt.fsf@gmail.com> (raw)
In-Reply-To: <83woin91sj.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 May 2019 19:15:40 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> +@node Autoload by Prefix
>> +@subsection Autoload by Prefix
>
> I think a "@cindex autoload by prefix" would be good here.
Sure.
>> +During completion for the commands @code{describe-variable} and
>> +@code{describe-function}, Emacs will try to load files which may
>> +contain definitions matching the prefix being completed. The variable
>> +@code{definition-prefixes} holds a hashtable which maps a prefix to
>> +the corresponding list of files to load for it. Entries to this
>> +mapping are added by calls to @code{register-definition-prefixes}
>> +which are generated by @code{update-file-autoloads}. Files which
>> +don't contain any definitions worth loading (test files, for
>> +examples), should set @code{autoload-compute-prefixes} to @code{nil}
>> +as a file-local variable.
>
> I would add a cross-reference to where update-file-autoloads is
> described after it's mentioned.
Um, how should I do this? I tried (I've also added
@anchor{update-file-autoloads} below @findex update-file-autoloads):
the corresponding list of files to load for it. Entries to this
mapping are added by calls to @code{register-definition-prefixes}
which are generated automatically (@pxref{update-file-autoloads,
@code{update-file-autoloads}}). Files which don't contain any
But it looks rather strange, it adds an extra period.
corresponding list of files to load for it. Entries to this mapping
are added by calls to `register-definition-prefixes' which are
generated automatically (*note `update-file-autoloads'
.). Files which don't contain any definitions
next prev parent reply other threads:[~2019-05-20 17:49 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-26 12:49 bug#28607: 27.0.50; help-fns unsolicited elisp loading Mark Oteiza
2017-09-26 15:40 ` Glenn Morris
2017-09-26 15:51 ` Mark Oteiza
2018-07-02 17:57 ` Eli Zaretskii
2018-07-02 18:05 ` Mark Oteiza
2018-07-02 18:16 ` Eli Zaretskii
2018-07-03 1:29 ` Glenn Morris
2018-07-16 13:03 ` Mark Oteiza
2019-05-16 2:12 ` Noam Postavsky
2019-05-16 13:38 ` Eli Zaretskii
2019-05-18 16:00 ` Noam Postavsky
2019-05-18 16:15 ` Eli Zaretskii
2019-05-20 17:49 ` Noam Postavsky [this message]
2019-05-20 19:01 ` Eli Zaretskii
2019-05-21 11:45 ` 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=875zq5audt.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=28607@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=mvoteiza@udel.edu \
/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).