emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#64292: closed (30.0.50; setf strange when lexical-binding is nil)


From: GNU bug Tracking System
Subject: bug#64292: closed (30.0.50; setf strange when lexical-binding is nil)
Date: Wed, 28 Jun 2023 18:33:02 +0000

Your message dated Wed, 28 Jun 2023 21:33:18 +0300
with message-id <831qhvv3m9.fsf@gnu.org>
and subject line Re: bug#64315: Acknowledgement (30.0.50; yasnippets not 
working due to change in bytecomp.el)
has caused the debbugs.gnu.org bug report #64315,
regarding 30.0.50; setf strange when lexical-binding is nil
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
64315: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=64315
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
--- Begin Message --- Subject: 30.0.50; setf strange when lexical-binding is nil Date: Mon, 26 Jun 2023 10:45:34 +0900 User-agent: Gnus/5.13 (Gnus v5.13) Emacs/30.0.50 (x86_64-pc-cygwin)
Hi,

In the *scratch* buffer:

(setq lexical-binding nil)
(require 'nnheader)
(macroexpand '(setf (mail-header-date header) date))
 => (let* ((v #'(lambda (cl-x) (progn (progn (aref cl-x 3)))))
           (v header))
      (\(setf\ funcall\) date v v))

This looks broken, though it gets normal if lexical-binding is t.
Because of this, an old ELisp module doesn't work.  In addition,
the funny portion is replaced with
\(setf\ internal--with-suppressed-warnings\)...
if the code is byte-compiled.

Thanks.

In GNU Emacs 30.0.50 (build 1, x86_64-pc-cygwin, GTK+ Version
 3.22.28, cairo version 1.17.4) of 2023-06-26 built on localhost



--- End Message ---
--- Begin Message --- Subject: Re: bug#64315: Acknowledgement (30.0.50; yasnippets not working due to change in bytecomp.el) Date: Wed, 28 Jun 2023 21:33:18 +0300
> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
> Date: Wed, 28 Jun 2023 18:48:19 +0200
> Cc: 64315@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
> 
> Yes, that did it! Thanks a ton, /PA

Thanks for testing, I'm closing the bug.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]