From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: michael_heerdegen@web.de, Lars Ingebrigtsen <larsi@gnus.org>,
24542@debbugs.gnu.org, npostavs@users.sourceforge.net
Subject: bug#24542: 25.1.50; The symbol `@' and sexp scanning
Date: Fri, 04 Sep 2020 10:22:41 -0400 [thread overview]
Message-ID: <jwvr1rhfx26.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83h7sdu0qf.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 04 Sep 2020 16:31:52 +0300")
>> Does anybody have any comments here?
> Stefan, any comments?
Checking for an immediately following word or symbol syntax doesn't see
sufficient if we consider cases like:
'(sgasfg)
or
, (sfgsdf)
or
,@ ;; entertained yet?
\)
and then we have the really fun stuff like:
(foo '@ bar)
vs
(foo ,@ bar)
So maybe a better solution is a syntax-propertize rule which
distinguishes "@ after comma" from "@ not after comma"?
Stefan
next prev parent reply other threads:[~2020-09-04 14:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-25 17:42 bug#24542: 25.1.50; The symbol `@' and sexp scanning Michael Heerdegen
2017-01-02 16:58 ` Michael Heerdegen
2017-01-02 20:37 ` npostavs
2017-01-03 12:46 ` Michael Heerdegen
2017-01-03 13:03 ` npostavs
2020-09-04 13:05 ` Lars Ingebrigtsen
2020-09-04 13:31 ` Eli Zaretskii
2020-09-04 14:22 ` Stefan Monnier [this message]
2024-04-10 23:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-11 3:42 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 17:29 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-12 21:32 ` Michael Heerdegen via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-13 1:55 ` 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=jwvr1rhfx26.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=24542@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=michael_heerdegen@web.de \
--cc=npostavs@users.sourceforge.net \
/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).