From: akrl--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: 46159@debbugs.gnu.org
Cc: mah@everybody.org
Subject: bug#46159: 28.0.50; lexical-let does not work with returned closures on nativecomp
Date: Thu, 28 Jan 2021 20:57:13 +0000 [thread overview]
Message-ID: <xjfft2kwziu.fsf@sdf.org> (raw)
In-Reply-To: <87h7n0akli.fsf@everybody.org> (mah's message of "Thu, 28 Jan 2021 15:10:33 -0500")
mah--- via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> I previously filed #45056 but the problem seemed to be fixed.
>
> It has re-appeared and I just noticed some interesting messages in my
> *Warnings* buffer that appear to be relevant.
>
> Specifically:
>
> Warning (comp): init.el:164:39: Warning: ‘(post-cmd post-cmd)’ is a malformed function
> Warning (comp): init.el:181:59: Warning: reference to free variable ‘rsync-buff’
>
> That section of code has this function:
>
> (defun mah/firestarter-sentinel (host post-cmd)
> "Sentinal function that will run the POST-CMD on HOST."
> (lexical-let ((post-cmd post-cmd)
> (host host)
> (rsync-buff (get-buffer-create mah/rsync-buff-name)))
> (lambda (proc event-type)
> (message (concat "post cmd: " post-cmd "\nevent: " event-type))
> (cond ((string-equal event-type "finished\n")
> (if post-cmd
> (progn (message (concat "rsync finished, running "
> post-cmd))
> (mah/firestarter-do-post host post-cmd rsync-buff))
> (message "rsync finshed")))
> (t (if post-cmd
> (progn (message (concat "rsync didn't finish normally, "
> "running anyway. Check "
> mah/rsync-buff-name))
> (mah/firestarter-do-post host post-cmd rsync-buff))
> (message "rsync finshed with errors")))))))
>
> I just compiled emacs from master and it did not exhibit the same behavior
Hi,
do we have a reproducer? Where is possible to see the whole file being
compiled?
Could you post all the warning in the *Async-native-compile-log* emitted
compiling init.el?
Dumb question: is this file requiring all necessary libraries (ex
‘cl.el’)?
Thanks!
Andrea
next prev parent reply other threads:[~2021-01-28 20:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 20:10 bug#46159: 28.0.50; lexical-let does not work with returned closures on nativecomp mah--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-01-28 20:57 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-01-28 21:20 ` Mark A. Hershberger
2021-01-28 21:24 ` akrl--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=xjfft2kwziu.fsf@sdf.org \
--to=bug-gnu-emacs@gnu.org \
--cc=46159@debbugs.gnu.org \
--cc=akrl@sdf.org \
--cc=mah@everybody.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.
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.