all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Basil L. Contovounesios" <contovob@tcd.ie>
To: Gregory Heytings <gregory@heytings.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
	Pedro Andres Aranda Gutierrez <paaguti@gmail.com>,
	emacs-devel@gnu.org
Subject: Re: New warnings compiling emacs just now
Date: Thu, 22 Apr 2021 10:06:01 +0100	[thread overview]
Message-ID: <87zgxq4rk6.fsf@tcd.ie> (raw)
In-Reply-To: <a87041afcb8e4e04c52b@heytings.org> (Gregory Heytings's message of "Thu, 22 Apr 2021 07:45:58 +0000")

Gregory Heytings <gregory@heytings.org> writes:

>>> I'm compiling Emacs master right now (on macOS Catalina) and have detected a
>>> couple of warnings 'assignment to free variable repeat-map' (one in
>>> tab-bar.el and one in window.el) Which I haven't seen before...
>>
>> I don't see any warnings, so please show the warnings you see.
>
> I see them (and have seen them for a week or two), too:
>
> In toplevel form:
> tab-bar.el:2093:33: Warning: assignment to free variable ‘repeat-map’
> In toplevel form:
> window.el:10261:33: Warning: assignment to free variable ‘repeat-map’

Isn't this just the usual case of a stale lisp/ldefs-boot.el?  IOW, I'd
expect the warnings to go away when that file is updated to include the
repeat-map autoload.

-- 
Basil



  reply	other threads:[~2021-04-22  9:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-22  5:22 New warnings compiling emacs just now Pedro Andres Aranda Gutierrez
2021-04-22  7:15 ` Eli Zaretskii
2021-04-22  7:45   ` Gregory Heytings
2021-04-22  9:06     ` Basil L. Contovounesios [this message]
2021-04-22  9:19       ` Gregory Heytings
2021-04-22  9:43         ` Eli Zaretskii
2021-04-22  9:53           ` Basil L. Contovounesios
2021-04-22 10:06             ` Gregory Heytings
2021-04-22  9:49         ` Gregory Heytings
2021-04-22 22:28           ` Juri Linkov

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=87zgxq4rk6.fsf@tcd.ie \
    --to=contovob@tcd.ie \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=gregory@heytings.org \
    --cc=paaguti@gmail.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 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.