From: Aaron Jensen <aaronjensen@gmail.com>
To: "Gerd Möllmann" <gerd.moellmann@gmail.com>
Cc: monnier@iro.umontreal.ca, 67991@debbugs.gnu.org
Subject: bug#67991: 30.0.50; boundp always returns nil in format-mode-line with let* after 0fde935
Date: Sat, 23 Dec 2023 10:52:22 -0500 [thread overview]
Message-ID: <CAHyO48zCg4ifPJd0i4apAurkui1OWjA-goUdGBeztd=0MobnZA@mail.gmail.com> (raw)
In-Reply-To: <m2r0jddjw7.fsf@Pro.fritz.box>
On Sat, Dec 23, 2023 at 10:21 AM Gerd Möllmann <gerd.moellmann@gmail.com> wrote:
>
> Aaron Jensen <aaronjensen@gmail.com> writes:
>
> > After commits:
> >
> > 0fde935b66e43e4d7ec137ba6195de993168587a
> > a63b206fbde2ead91f1053d80a275f8850e5ffce
> >
> > boundp returns nil here, rather than t, like it used to:
> >
> > (format-mode-line
> > '(:eval (let* ((some-var "some-value")
> > (_ (message "Bound: %S" (boundp 'some-var))))
> > (message "Var: %S, Bound: %S" some-var (boundp 'some-var)))))
> >
> > This has an impact on a particular package I use for my modeline, which
> > can be worked around if this behavior is expected. It seemed a
> > significant chagne, so I wanted to report it, in case it was not expected.
>
> I don't know why that would have changed things with Stefan's commit,
> but are your sure that some-var is declared special (has a defvar, for
> instance)? When it is, boundp returns t here.
It's not in the package in question. But even if I defvar w/o giving
it a value, it does not return t:
(defvar some-var)
(let* ((some-var "some-value")
(_ (message "Bound: %S" (boundp 'some-var))))
(message "Var: %S, Bound: %S" some-var (boundp 'some-var)))
(format-mode-line
'(:eval (let* ((some-var "some-value")
(_ (message "Bound: %S" (boundp 'some-var))))
(message "Var: %S, Bound: %S" some-var (boundp 'some-var)))))
The first returns t, the second does not.
As to your question, Eli, I don't know. If it shouldn't return nil
then I can report that downstream and they can fix it there.
Aaron
next prev parent reply other threads:[~2023-12-23 15:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-23 14:51 bug#67991: 30.0.50; boundp always returns nil in format-mode-line with let* after 0fde935 Aaron Jensen
2023-12-23 15:09 ` Eli Zaretskii
2023-12-23 15:21 ` Gerd Möllmann
2023-12-23 15:52 ` Aaron Jensen [this message]
2023-12-23 16:13 ` Gerd Möllmann
2023-12-23 16:42 ` Eli Zaretskii
2023-12-24 7:13 ` Gerd Möllmann
2023-12-24 7:45 ` Eli Zaretskii
2023-12-24 8:05 ` Gerd Möllmann
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='CAHyO48zCg4ifPJd0i4apAurkui1OWjA-goUdGBeztd=0MobnZA@mail.gmail.com' \
--to=aaronjensen@gmail.com \
--cc=67991@debbugs.gnu.org \
--cc=gerd.moellmann@gmail.com \
--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).