From: Lars Ingebrigtsen <larsi@gnus.org>
To: Phil Sainty <psainty@orcon.net.nz>
Cc: 52290@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#52290: 28.0.90; Undocumented generalized variables
Date: Sun, 05 Dec 2021 03:46:11 +0100 [thread overview]
Message-ID: <87mtlfu5u4.fsf@gnus.org> (raw)
In-Reply-To: <c256d6e2137c14e6bbb0c4ccb1117176@webmail.orcon.net.nz> (Phil Sainty's message of "Sun, 05 Dec 2021 15:09:09 +1300")
Phil Sainty <psainty@orcon.net.nz> writes:
> I guess we'd want a new define-obsolete-* function, and for the setf
> macro to be flagging uses of obsolete PLACE forms at compile time?
Yup.
> It looks to me as if `gv-get' might be the right place to be checking
> this (but I'm only looking at the internals for the first time and
> don't have a good handle on this stuff).
Perhaps Stefan has some opinions here.
> Fair enough. Should we start by deciding which ones we *should*
> document, and at least get that much added for 28.1?
>
> `buffer-local-value' is a clear "yes" vote from me (and I don't
> currently have an opinion on anything else).
Yes, `buffer-local-value' seems useful.
I think we should implement the obsoletion mechanism and then just go
through that list and obsolete all the stuff that doesn't seem useful
(and isn't used in-tree). And then document the rest, as well as make
the *Help* buffer mention that they're generalised variables.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-12-05 2:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-05 1:25 bug#52290: 28.0.90; Undocumented generalized variables Phil Sainty
2021-12-05 1:35 ` Lars Ingebrigtsen
2021-12-05 1:55 ` Michael Heerdegen
2021-12-05 2:00 ` Lars Ingebrigtsen
2021-12-05 2:25 ` Michael Heerdegen
2021-12-05 2:52 ` Lars Ingebrigtsen
2021-12-05 16:17 ` Michael Heerdegen
2021-12-05 20:43 ` Lars Ingebrigtsen
2021-12-05 2:09 ` Phil Sainty
2021-12-05 2:46 ` Lars Ingebrigtsen [this message]
2022-08-21 22:36 ` Lars Ingebrigtsen
2022-08-23 0:07 ` Michael Heerdegen
2022-08-23 10:41 ` Lars Ingebrigtsen
2022-08-31 2:10 ` Michael Heerdegen
2022-08-31 9:58 ` Lars Ingebrigtsen
2022-10-04 11:58 ` Lars Ingebrigtsen
2021-12-06 4:33 ` Richard Stallman
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=87mtlfu5u4.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=52290@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=psainty@orcon.net.nz \
/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).