From: Ignacio Casso <ignaciocasso@hotmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, larsi@gnus.org, 54399@debbugs.gnu.org,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#54399: 27.2; Problems with (let ((custom-variable ...)) (autoload-function ...))
Date: Tue, 12 Apr 2022 14:16:34 +0200 [thread overview]
Message-ID: <PAXPR06MB77602F0D4C19E0252B6EA52DC6ED9@PAXPR06MB7760.eurprd06.prod.outlook.com> (raw)
In-Reply-To: <8335ii5y60.fsf@gnu.org>
> Please tell more in each case where you consider the behavior
> "surprising" why did you expect something different. I think it's
> important to make the subsequent discussion focused and efficient.
>
> Thanks.
I explained why I considered some of those cases surprising by
themselves in previous emails of the thread. I originally expected
`default-value', `set-default' and `default-boundp' to behave like their
counterparts `default-toplevel-value' and
`set-default-toplevel-value'. But I assumed there was a reason for there
being two versions, so I was just going to update some docstrings to
make the distinction more clear (or in the case `default-boundp',
correct the docstring, which is just wrong).
But now, considering all the cases together, I also consider surprising
that the behavior, whichever the correct one should be, depends on
whether the variable has or not a buffer local binding. So for example,
for the following
> ;; default defined, buffer-local undefined
> (defvar var1 "default")
> (let ((var1 "inside let")) (default-value 'var1)) ;; returns "inside let"
>
> ;; default defined, buffer-local defined
> (defvar var2 "default")
> (setq-local var2 "buffer-local")
> (let ((var2 "inside let")) (default-value 'var2)) ;; returns "default"
I would expect both snippets to return the same. And the same goes for
every two pair of snippets that only differ in whether the form
(setq-local varX "buffer-local") is present. So I was no longer sure
that the issue was just incomplete or ambiguous documentation, and I
wrote all the cases I could think in the last email to see what you
think about it.
P.S. By the way, I had deleted the previous emails on these thread, so I
could not properly reply to the last one, and had to just write to
54399@debbugs.gnu.org instead. What is the proper way to reply to an
debbugs email thread that is no longer or never was in your inbox? For
the org-mode mail list there is a link on the web archives, but not for
debbugs.gnu.org. Is there a quick way from the debbugs package? Or maybe
using some of the info in the mbox file, which can be downloaded from
the archives in debbugs.gnu.org? Thanks
next prev parent reply other threads:[~2022-04-12 12:16 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-15 11:50 bug#54399: 27.2; Problems with (let ((custom-variable ...)) (autoload-function ...)) Ignacio Casso
2022-03-17 11:23 ` Lars Ingebrigtsen
2022-03-18 0:22 ` Michael Heerdegen
2022-03-18 1:02 ` Michael Heerdegen
2022-03-18 9:32 ` Lars Ingebrigtsen
2022-03-18 9:38 ` Ignacio Casso
2022-04-12 13:18 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 13:23 ` Ignacio Casso
2022-04-12 13:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 9:13 ` Ignacio Casso
2022-04-12 11:38 ` Eli Zaretskii
2022-04-12 12:16 ` Ignacio Casso [this message]
2022-04-12 13:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 14:27 ` Ignacio Casso
2022-04-12 15:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 15:27 ` Ignacio Casso
2022-04-12 22:15 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-13 15:26 ` Ignacio Casso
2022-04-13 0:24 ` Michael Heerdegen
2022-04-13 3:26 ` Glenn Morris
2022-04-13 3:43 ` Michael Heerdegen
2022-04-12 15:24 ` Eli Zaretskii
2022-04-13 17:22 ` Ignacio Casso
2022-04-12 13:19 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-12 13:51 ` Ignacio Casso
2022-04-12 15:22 ` Eli Zaretskii
2022-04-13 0:06 ` Michael Heerdegen
2022-04-13 12:08 ` Ignacio Casso
2022-05-12 2:32 ` Lars Ingebrigtsen
2022-05-12 6:58 ` Ignacio Casso
2022-05-12 7:34 ` Eli Zaretskii
2022-05-12 8:14 ` Ignacio Casso
2022-05-12 8:36 ` Eli Zaretskii
2022-05-12 8:41 ` Ignacio Casso
2022-05-12 9:40 ` Eli Zaretskii
2022-05-12 11:49 ` Lars Ingebrigtsen
2022-06-09 15:02 ` Lars Ingebrigtsen
2022-06-09 21:19 ` Ignacio Casso
2022-06-10 9:13 ` Lars Ingebrigtsen
2022-06-10 14:01 ` dick
2022-06-11 10:51 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=PAXPR06MB77602F0D4C19E0252B6EA52DC6ED9@PAXPR06MB7760.eurprd06.prod.outlook.com \
--to=ignaciocasso@hotmail.com \
--cc=54399@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--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.