From: Michael Heerdegen <michael_heerdegen@web.de>
To: help-gnu-emacs@gnu.org
Subject: Re: closure within closure, incorrect (?) byte-compiler warnings
Date: Tue, 09 Nov 2021 01:04:12 +0100 [thread overview]
Message-ID: <875yt29oub.fsf@web.de> (raw)
In-Reply-To: 87o86u2pbo.fsf@zoho.eu
Emanuel Berg via Users list for the GNU Emacs text editor
<help-gnu-emacs@gnu.org> writes:
> This sums it up ... three bugs?
> ;; 1. Byte compiler warnings (two cases) relating to the
> ;; interactive spec:
> ;;
> ;; geh.el:7:1: Warning: Unused lexical variable `more-data'
> ;; geh.el:10:54: Warning: reference to free variable ‘data-item’
> ;; geh.el:10:64: Warning: reference to free variable ‘more-data’
> ;;
> ;; 2. When the compiled version is used interactively:
> ;;
> ;; Symbol's value as variable is void: data-item
These are all symptoms of one and the same issue: the interactive spec
currently can't refer to outer lexical variables. The warnings are
actually legitimate, they only warn about this limitation. So: one bug
(there was no Bug #3 in your list btw).
Michael.
next prev parent reply other threads:[~2021-11-09 0:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 7:06 closure within closure, incorrect (?) byte-compiler warnings Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-01 7:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-01 12:31 ` Stefan Monnier via Users list for the GNU Emacs text editor
2021-11-03 3:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-08 23:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-08 23:35 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-09 0:04 ` Michael Heerdegen [this message]
2021-11-09 0:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-11-10 4:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=875yt29oub.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=help-gnu-emacs@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.
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).