From: Stefan Monnier via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: contovob@tcd.ie, 44418@debbugs.gnu.org,
Yuan Fu <casouri@gmail.com>,
larsi@gnus.org, mattias.engdegard@gmail.com
Subject: bug#44418: 28.0.50; Spliced variable not matched as symbol in isearch
Date: Sun, 09 Jul 2023 08:36:39 -0400 [thread overview]
Message-ID: <jwv1qhhtgba.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83ilatbotd.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 09 Jul 2023 09:07:26 +0300")
>> I agree that it’s easy to figure out what does the detached @ syntax
>> mean. I mainly just don’t like having two ways to do the same thing.
>>
>> Since I don’t use search symbol myself, I can’t grasp the importance of
>> it. You apparently care about it enough to go this far, and I’m willing to
>> take your word for it.
>>
>> You mentioned sexp queries, which reminded me that using the detached
>> syntax would allow people to interpolate capture names with quasi
>> quotes. That’s a plus for the detached syntax.
>>
>> Ultimately I’m still on the fence for this. But if you still want to add it, please go ahead :-)
>
> I'd like to hear Stefan's opinion on this, before we make such a
> change (if we make it).
Yuan knows this area much better than I do, and I fully trust his
judgment on this.
The only I'd point out is that if we introduce a (@ ...) syntax here
we should try and phase out the old @... syntax, i.e. emit an
obsolescence warning when we bump into such code.
Stefan
next prev parent reply other threads:[~2023-07-09 12:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 15:38 bug#44418: 28.0.50; Spliced variable not matched as symbol in isearch Basil L. Contovounesios
2022-06-07 10:29 ` Lars Ingebrigtsen
2022-06-07 12:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-07 17:45 ` Lars Ingebrigtsen
2022-06-07 18:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-07 18:28 ` Lars Ingebrigtsen
2022-06-08 12:29 ` Lars Ingebrigtsen
2023-06-21 15:59 ` Mattias Engdegård
2023-06-21 17:15 ` Eli Zaretskii
2023-06-22 8:50 ` Mattias Engdegård
2023-06-22 10:11 ` Eli Zaretskii
2023-06-22 11:24 ` Mattias Engdegård
2023-06-23 11:58 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-06-23 12:06 ` Mattias Engdegård
2023-06-23 16:54 ` Mattias Engdegård
2023-06-23 22:39 ` Yuan Fu
2023-06-24 6:39 ` Eli Zaretskii
2023-06-24 10:12 ` Mattias Engdegård
2023-06-25 11:38 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-08 23:48 ` Yuan Fu
2023-07-09 6:07 ` Eli Zaretskii
2023-07-09 12:36 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-07-12 15:09 ` Dmitry Gutov
2023-07-12 14:46 ` Mattias Engdegård
2023-07-12 15:26 ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-07-18 1:54 ` Dmitry Gutov
2023-07-18 8:35 ` Basil Contovounesios 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=jwv1qhhtgba.fsf-monnier+emacs@gnu.org \
--to=bug-gnu-emacs@gnu.org \
--cc=44418@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=contovob@tcd.ie \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=mattias.engdegard@gmail.com \
--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).