From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 51695@debbugs.gnu.org
Subject: bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue
Date: Tue, 09 Nov 2021 08:14:03 -0500 [thread overview]
Message-ID: <jwvilx11nqs.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <87k0hi2p3i.fsf@zoho.eu> (Emanuel Berg's message of "Tue, 09 Nov 2021 00:40:33 +0100")
> (this should sum it up but see thread on gmane.emacs.help for background,
> https://lists.gnu.org/archive/html/help-gnu-emacs/2021-11/msg00000.html
> . keep it real)
>
> ;;; -*- lexical-binding: t -*-
> ;;;
> ;;; this file:
> ;;; http://user.it.uu.se/~embe8573/emacs-init/geh.el
> ;;; https://dataswamp.org/~incal/emacs-init/geh.el
>
> (let ((data-item 1)
> (more-data 2) )
> (defun echo-data (&optional data)
> (interactive (list (read-number "number: " (or data-item more-data))))
> (message "data: %s" (or data data-item)) ))
> ;; (echo-data 5)
> ;; (echo-data)
> ;; (call-interactively #'echo-data)
>
> ;; Emacs 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
Thanks. This is a limitation in `cconv.el` tho it will likely require
further changes in `bytecomp.el` and/or `callint.c`.
Not sure when I'll find the time to tackle it, so in the mean time
I recommend you find some workaround,
Stefan
next prev parent reply other threads:[~2021-11-09 13:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-08 23:40 bug#51695: 29.0.50; lexical scope closure, interactive spec byte compiler warnings/usage issue Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-09 12:29 ` Eli Zaretskii
2021-11-10 1:39 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 1:54 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 13:20 ` Eli Zaretskii
2021-11-09 13:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-11-09 23:32 ` Michael Heerdegen
2021-11-10 1:50 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 4:13 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-10 23:44 ` Michael Heerdegen
2021-11-11 1:55 ` Emanuel Berg via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-11-11 4:14 ` Michael Heerdegen
2022-09-20 12:13 ` Lars Ingebrigtsen
2022-09-23 20:37 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-09-24 10:31 ` Lars Ingebrigtsen
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=jwvilx11nqs.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=51695@debbugs.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 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).