From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 44418@debbugs.gnu.org
Subject: bug#44418: 28.0.50; Spliced variable not matched as symbol in isearch
Date: Tue, 07 Jun 2022 19:45:16 +0200 [thread overview]
Message-ID: <871qw0e5ar.fsf@gnus.org> (raw)
In-Reply-To: <jwvmteollxv.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 07 Jun 2022 08:05:31 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> `@x` is a valid symbol, which is why `?@` is given symbol syntax.
> If we want to fix the above search we need to use
> `syntax-propertize-function` to change the syntax of those `@` that
> follow a comma.
The following seems to do the trick -- does this look OK to you?
diff --git a/lisp/progmodes/elisp-mode.el b/lisp/progmodes/elisp-mode.el
index 77bf3f1ed1..210270bc67 100644
--- a/lisp/progmodes/elisp-mode.el
+++ b/lisp/progmodes/elisp-mode.el
@@ -245,6 +245,9 @@ elisp-mode-syntax-propertize
;; Empty symbol.
("##" (0 (unless (nth 8 (syntax-ppss))
(string-to-syntax "_"))))
+ ;; Give ,@ a prefix syntax.
+ (",@" (0 (unless (ppss-comment-or-string-start (syntax-ppss))
+ (string-to-syntax "'"))))
;; Unicode character names. (The longest name is 88 characters
;; long.)
("\\?\\\\N{[-A-Za-z0-9 ]\\{,100\\}}"
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-07 17:45 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 [this message]
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
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=871qw0e5ar.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=44418@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--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).