From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 65347@debbugs.gnu.org, monnier@iro.umontreal.ca
Subject: bug#65347: 29.1; Underscore in query replace prevents case-matching
Date: Sat, 19 Aug 2023 09:00:37 +0300 [thread overview]
Message-ID: <83h6ov3722.fsf@gnu.org> (raw)
In-Reply-To: <iersf8gnk0z.fsf@janestreet.com> (message from Spencer Baugh on Fri, 18 Aug 2023 17:00:12 -0400)
> From: Spencer Baugh <sbaugh@janestreet.com>
> Cc: 65347@debbugs.gnu.org, monnier@iro.umontreal.ca
> Date: Fri, 18 Aug 2023 17:00:12 -0400
>
> > We should work on adding refactoring instead of tweaking M-% and M-*
> > in these directions.
>
> Okay, I'm convinced. I'll defer this functionality to the future
> refactoring support in Emacs, built with project.el and eglot no doubt.
Eglot can serve as the back-end, and it isn't the only one that comes
to mind (I sincerely hope that at least some of the simpler
refactoring jobs will not require an LSP, but could be done using
built-in capabilities).
But back-end is just one part of this. We should IMO begin by our own
research into the UI parts of this: how does the user specify the
requested refactoring? Several alternatives are possible, and we
should study them and decide what is best for Emacs.
Would someone please step forward and work on adding refactoring to
Emacs?
next prev parent reply other threads:[~2023-08-19 6:00 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-16 21:27 bug#65347: 29.1; Underscore in query replace prevents case-matching Spencer Baugh
2023-08-17 7:14 ` Eli Zaretskii
2023-08-17 12:42 ` Spencer Baugh
2023-08-17 13:26 ` Eli Zaretskii
2023-08-18 2:04 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-18 6:04 ` Eli Zaretskii
2023-08-18 16:30 ` Spencer Baugh
2023-08-18 18:15 ` Eli Zaretskii
2023-08-18 18:31 ` Spencer Baugh
2023-08-18 19:06 ` Eli Zaretskii
2023-08-18 19:14 ` Spencer Baugh
2023-08-18 19:29 ` Eli Zaretskii
2023-08-18 21:00 ` Spencer Baugh
2023-08-19 6:00 ` Eli Zaretskii [this message]
2023-08-21 1:13 ` Richard Stallman
2023-08-18 19:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 5:50 ` Eli Zaretskii
2023-08-19 14:39 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 14:50 ` Eli Zaretskii
2023-08-19 15:51 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 19:14 ` Eli Zaretskii
2023-08-20 0:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 14:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-08-19 15:01 ` Eli Zaretskii
2023-08-19 16:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6ov3722.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=65347@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sbaugh@janestreet.com \
/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.