From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 74615-done@debbugs.gnu.org, mail@daniel-mendler.de, dancol@dancol.org
Subject: bug#74615: 30.0.92; js-find-symbol automatically activates ido-mode
Date: Sat, 07 Dec 2024 14:54:09 +0200 [thread overview]
Message-ID: <86msh7irgu.fsf@gnu.org> (raw)
In-Reply-To: <jwved2sim0q.fsf-monnier+emacs@gnu.org> (message from Stefan Monnier on Sat, 30 Nov 2024 14:05:14 -0500)
> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Cc: Daniel Mendler <mail@daniel-mendler.de>, Daniel Colascione
> <dancol@dancol.org>, 74615@debbugs.gnu.org
> Date: Sat, 30 Nov 2024 14:05:14 -0500
>
> > This code is there since the day js.el was added, so I don't think
> > removing the activation of ido-mode is something we can do, because
> > users might expect that by now.
>
> User backward-compatibility is nice but not important enough to imply
> "cannot do". I think in this case, IDO has lost enough popularity by
> now that more users will be happy rather than annoyed by the change.
>
> > Maybe we could make that optional or something.
>
> Users can enable IDO already, and if really some users like IDO for this
> command but not elsewhere (which seems highly unlikely to me), we can
> add a small ELisp snippet in NEWS using `advice-add`, for them to copy
> to their init file.
Sounds like there's consensus to make this change, so I've now
installed it on the master branch, and I'm therefore closing this bug.
prev parent reply other threads:[~2024-12-07 12:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-30 6:37 bug#74615: 30.0.92; js-find-symbol automatically activates ido-mode Daniel Mendler via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-30 8:02 ` Eli Zaretskii
2024-11-30 16:18 ` Daniel Colascione
2024-11-30 17:05 ` Dmitry Gutov
2024-11-30 19:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 12:54 ` Eli Zaretskii [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=86msh7irgu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74615-done@debbugs.gnu.org \
--cc=dancol@dancol.org \
--cc=mail@daniel-mendler.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 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).