From: Stefan Kangas <stefankangas@gmail.com>
To: Ikumi Keita <ikumi@ikumi.que.jp>
Cc: 61210-done@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#61210: 28.2; Request to modify code which can accidentally overwrite AUCTeX function
Date: Wed, 6 Sep 2023 01:02:23 -0700 [thread overview]
Message-ID: <CADwFkm=8nrPWAg31_GmXVEBsg+KOGt3hjSvoxSA=C+dOoP40iA@mail.gmail.com> (raw)
In-Reply-To: <87901.1693980537@localhost>
Ikumi Keita <ikumi@ikumi.que.jp> writes:
> Hi Stefan,
>
>>>>>> Stefan Kangas <stefankangas@gmail.com> writes:
>> From skimming this bug report, it seems like all the issues were
>> resolved here? Or is there anything left to do?
>
> As a longer term goal, it would be ideal to remove the current autoloads
> in my opinion. However, if it is considered difficult to do so for some
> reason (e.g. keeping backward compatibility), I don't mind much.
I think it will be a breaking change unfortunately. To do it safely,
we'd have to obsolete the relevant functions, and introduce new ones
that are not autoloaded. Which I guess is not ideal here.
I'm closing this bug for now. If you can think of anything else, please
reopen this bug or file a new one.
Thanks.
next prev parent reply other threads:[~2023-09-06 8:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-01 12:13 bug#61210: 28.2; Request to modify code which can accidentally overwrite AUCTeX function Ikumi Keita
2023-03-18 22:35 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 12:25 ` Ikumi Keita
2023-03-20 15:07 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-20 17:44 ` Ikumi Keita
2023-09-05 23:29 ` Stefan Kangas
2023-09-06 6:08 ` Ikumi Keita
2023-09-06 8:02 ` Stefan Kangas [this message]
2023-09-12 21:50 ` 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
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='CADwFkm=8nrPWAg31_GmXVEBsg+KOGt3hjSvoxSA=C+dOoP40iA@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=61210-done@debbugs.gnu.org \
--cc=ikumi@ikumi.que.jp \
--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).