From: Drew Adams <drew.adams@oracle.com>
To: Michael Heerdegen <michael_heerdegen@web.de>, jixiuf <jixiuf@qq.com>
Cc: 45619@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#45619: 28.0.50; pcase-let on MacOS doesn't work
Date: Mon, 4 Jan 2021 15:41:19 +0000 (UTC) [thread overview]
Message-ID: <b2285859-030c-4f84-98ae-15df7b8c960c@default> (raw)
In-Reply-To: <877dos50su.fsf@web.de>
> > (pcase-let ((`(,default-directory) '( "/tmp/")))
> > (call-interactively 'find-file))
> >
> > Expected behavior: Find file in "/tmp/"
> > Observed behavior: Find file in "~"
>
> AFAICT the issue here is that `pcase-let' always creates lexically
> scoped bindings, even for special variables. That can be surprising.
>
> @Stefan, what can we do? Document better? Add compiler warnings? Or
> is it possible to "fix" this?
Please do at least document it (along with the reason for it perhaps?).
What is the reason for it, BTW?
next prev parent reply other threads:[~2021-01-04 15:41 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-03 7:59 bug#45619: 28.0.50; pcase-let on MacOS doesn't work jixiuf
2021-01-04 12:44 ` Michael Heerdegen
2021-01-04 15:41 ` Drew Adams [this message]
2021-01-04 17:41 ` Stefan Monnier
2021-01-04 19:50 ` Michael Heerdegen
2021-01-04 20:37 ` Stefan Monnier
2021-01-04 22:08 ` Michael Heerdegen
2021-01-05 2:06 ` Stefan Monnier
2021-01-07 11:38 ` Michael Heerdegen
2021-01-07 15:19 ` Stefan Monnier
2021-01-08 20:05 ` Michael Heerdegen
2021-01-08 22:13 ` Stefan Monnier
2022-02-12 7:46 ` Lars Ingebrigtsen
2022-02-12 14:56 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 16:30 ` Lars Ingebrigtsen
2022-02-12 17:10 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-02-12 17:21 ` Lars Ingebrigtsen
2022-02-12 22:33 ` Stefan Monnier 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=b2285859-030c-4f84-98ae-15df7b8c960c@default \
--to=drew.adams@oracle.com \
--cc=45619@debbugs.gnu.org \
--cc=jixiuf@qq.com \
--cc=michael_heerdegen@web.de \
--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 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.