From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: emacs-devel@gnu.org, me@eshelyaron.com
Subject: Re: master 47e313e9805: Unbind 'C-M-i' in Text mode
Date: Thu, 30 Nov 2023 10:41:01 +0200 [thread overview]
Message-ID: <83wmtzbplu.fsf@gnu.org> (raw)
In-Reply-To: <m234wnk7ts.fsf@macmutant.fritz.box> (message from Arash Esbati on Thu, 30 Nov 2023 08:40:15 +0100)
> From: Arash Esbati <arash@gnu.org>
> Cc: emacs-devel@gnu.org, me@eshelyaron.com
> Date: Thu, 30 Nov 2023 08:40:15 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > It's a bogus warning, it happens because you build Emacs
> > incrementally, starting from the previous build.
>
> Actually, I use a small script which does:
>
> git clean -fdx --exclude=ChangeLog
> ./autogen.sh
> ./configure ...
> make
>
> So I don't build incrementally. And I thought the method above is
> (almost?) equivalent to "make bootstrap"
>
> > To make sure, say
> >
> > touch lisp/textmodes/text-mode.el
> >
> > and then say "make" again -- this time there will be no warning.
>
> True, that works.
>
> > AFAICT, the problem is that the first time loaddefs.el still isn't
> > updated, or something like that.
> >
> > Such temporary warnings appear very frequently when Emacs is built
> > after an update (as opposed to a "make bootstrap").
>
> I get the warnings (see other message) also with "make bootstrap".
If so, then a declare-function might indeed be necessary.
next prev parent reply other threads:[~2023-11-30 8:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <170099515102.15929.4538081255360222923@vcs2.savannah.gnu.org>
[not found] ` <20231126103911.6CEAFC25D5B@vcs2.savannah.gnu.org>
2023-11-29 19:11 ` master 47e313e9805: Unbind 'C-M-i' in Text mode Arash Esbati
2023-11-30 6:07 ` Eli Zaretskii
2023-11-30 7:40 ` Arash Esbati
2023-11-30 8:41 ` Eli Zaretskii [this message]
2023-11-30 10:46 ` Arash Esbati
2023-11-30 17:17 ` Juri Linkov
2023-12-05 23:26 ` Dmitry Gutov
2023-12-06 7:53 ` Eshel Yaron
2023-12-06 12:45 ` Dmitry Gutov
2023-12-06 13:56 ` Eshel Yaron
2023-12-06 14:33 ` Dmitry Gutov
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=83wmtzbplu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=me@eshelyaron.com \
/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).