From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Ihor Radchenko <yantar92@posteo.net>
Cc: 66946-done@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#66946: 30.0.50; Elisp manual section 17.4 describes an obsolete variable
Date: Sat, 17 Aug 2024 05:53:43 -0700 [thread overview]
Message-ID: <CADwFkmm_Ahz=Fh1z6OHapjvZsL-qv87kk71Gd8ScDEMeaTGvdQ@mail.gmail.com> (raw)
In-Reply-To: <86sev332tu.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> Cc: 66946@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
>> From: Ihor Radchenko <yantar92@posteo.net>
>> Date: Mon, 12 Aug 2024 06:18:18 +0000
>>
>> Stefan Kangas <stefankangas@gmail.com> writes:
>>
>> > Why not throw away the code if it's hardly measurable? We could make it
>> > a no-op in Emacs 30.1, and then just remove it from the manual. It's
>> > already been obsolete for three major versions by then.
>>
>> Just bumping this thread, so that it is not lost ahead of the release.
>
> I think we lost focus and context. What exactly is being proposed now
> for the upcoming Emacs 30 release?
I think the idea was to remove the obsolete variable
`byte-compile-dynamic` from the manual. This has already been done in
emacs-30.
The variable is still there but is marked obsolete and documented as
having no effect. It will get removed in some future release of Emacs;
there is no particular rush with deleting it.
I'm therefore boldly closing this bug report.
prev parent reply other threads:[~2024-08-17 12:53 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-05 9:37 bug#66946: 30.0.50; Elisp manual section 17.4 describes an obsolete variable Ihor Radchenko
2023-11-05 14:23 ` Stefan Kangas
2023-11-05 23:24 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06 0:21 ` Stefan Kangas
2024-01-11 21:52 ` Stefan Kangas
2024-08-12 6:18 ` Ihor Radchenko
2024-08-17 9:39 ` Eli Zaretskii
2024-08-17 12:53 ` Stefan Kangas [this message]
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='CADwFkmm_Ahz=Fh1z6OHapjvZsL-qv87kk71Gd8ScDEMeaTGvdQ@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=66946-done@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=yantar92@posteo.net \
/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).