From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Noam Postavsky <npostavs@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Shigeru Fukaya <shigeru.fukaya@gmail.com>,
15998@debbugs.gnu.org
Subject: bug#15998: 24.3; forward-sexp (scan-sexps) doesn't do well with some SEXPs
Date: Sun, 07 Jul 2019 09:28:08 -0400 [thread overview]
Message-ID: <jwvk1cuasg5.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <875zoe4mvs.fsf@gmail.com> (Noam Postavsky's message of "Sat, 06 Jul 2019 22:08:39 -0400")
>> No, but I think syntax-propertize can take care of those things.
> The patch below seems to work, no new sexp movement commands needed?
It should work indeed, tho I'm not sure it'll fix the original problem,
because I don't know *where* the original problem happened and this
patch only fixes the case where we do such navigation in
emacs-lisp-mode, but things #s(...) and #&"..." are *very* rare in
those buffers.
So I'm not completely sure the cost imposed by this patch is worth
the benefit. Maybe we could start by adding those rules to the
elisp-byte-code-mode?
Stefan
next prev parent reply other threads:[~2019-07-07 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-29 14:45 bug#15998: 24.3; forward-sexp (scan-sexps) doesn't do well with some SEXPs Shigeru Fukaya
2013-11-29 17:12 ` Stefan Monnier
2013-12-01 20:08 ` Shigeru Fukaya
2013-12-01 20:44 ` Stefan Monnier
2013-12-03 9:47 ` Shigeru Fukaya
2013-12-03 17:09 ` Stefan Monnier
2019-06-26 15:23 ` Lars Ingebrigtsen
2019-06-26 17:06 ` Stefan Monnier
2019-06-27 10:30 ` Lars Ingebrigtsen
2019-07-07 2:08 ` Noam Postavsky
2019-07-07 13:28 ` Stefan Monnier [this message]
2019-07-07 13:47 ` Noam Postavsky
2022-05-06 15:50 ` bug#30132: 27.0.50; scan-sexps and ## Lars Ingebrigtsen
2022-05-06 16:30 ` bug#15998: " Lars Ingebrigtsen
2022-05-07 0:08 ` Michael Heerdegen
2022-05-07 4:05 ` bug#15998: " Michael Heerdegen
2022-05-07 10:17 ` Lars Ingebrigtsen
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=jwvk1cuasg5.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=15998@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=npostavs@gmail.com \
--cc=shigeru.fukaya@gmail.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 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).