From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca
Subject: Re: master 60c9702972f: * lisp/help.el (help--analyze-key): Use `help-fns-function-name`
Date: Sat, 30 Mar 2024 19:40:16 +0300 [thread overview]
Message-ID: <86a5mfd66n.fsf@gnu.org> (raw)
In-Reply-To: <m2y19zraf5.fsf@macmutant.fritz.box> (message from Arash Esbati on Sat, 30 Mar 2024 16:45:02 +0100)
> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org, monnier@iro.umontreal.ca
> Date: Sat, 30 Mar 2024 16:45:02 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > This is not a real problem: after you build once, touch lisp.help.el
> > and build again: the warning will be gone. That's because the
> > autoload form for the function will be written to loaddefs.el.
>
> Thanks, does this also apply to a clean state repo? I use a small
> script to build Emacs which does:
>
> git clean -fdx --exclude=ChangeLog
> ./autogen.sh
> ./configure ...
>
> My lisp/loaddefs.el already has an entry:
>
> $ grep help-fns-function loaddefs.el
> (autoload 'help-fns-function-name "help-fns" "\
>
> I didn't change anything after my initial build where I reported the
> warning.
No clue, sorry. I got the warning upon the first build after update
from upstream, then the next build didn't have the warning.
next prev parent reply other threads:[~2024-03-30 16:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <171107186434.18812.2389706590800223024@vcs2.savannah.gnu.org>
[not found] ` <20240322014425.180EEC12C52@vcs2.savannah.gnu.org>
2024-03-30 11:19 ` master 60c9702972f: * lisp/help.el (help--analyze-key): Use `help-fns-function-name` Arash Esbati
2024-03-30 13:05 ` Eli Zaretskii
2024-03-30 15:45 ` Arash Esbati
2024-03-30 16:40 ` Eli Zaretskii [this message]
2024-03-31 2:55 ` Stefan Monnier
2024-03-31 14:28 ` Arash Esbati
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86a5mfd66n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.