From: ndame via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: Re: backward-sexp throws scan-error "Unbalanced parentheses", but forward-sexp works
Date: Thu, 13 Jan 2022 09:04:52 +0000 [thread overview]
Message-ID: <FaMRsQQmJ1mIiI6CglfUiw4PQZciyHO7f8i9R06HQSYLByhHbb1_5XGedoNGWWGVm38359s84WjSO_yYvw27dyMlisOtAOjymTSkPk9INoc=@protonmail.com> (raw)
In-Reply-To: <dQtcfOjRWSmrV91zxYjy2MofrlB9MMHvYJqTxFKnA0mSE7EaJM14Mbi_IEPffEtED-hgwR4TTP-xVlMUE690ezNzwjcozjtmMRLgRQtcUVE=@protonmail.com>
> Apparently, aggressive-indent-mode is the culprit. I can replicate the problem with -Q and aggressive-indent-mode turned on.
Reported the problem to aggressive-indent-mode author with steps how to reproduce:
https://github.com/Malabarba/aggressive-indent-mode/issues/153
We'll see what he can say about it.
next prev parent reply other threads:[~2022-01-13 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-12 16:49 backward-sexp throws scan-error "Unbalanced parentheses", but forward-sexp works ndame via Users list for the GNU Emacs text editor
2022-01-12 17:33 ` ndame via Users list for the GNU Emacs text editor
2022-01-12 21:06 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-13 5:40 ` ndame via Users list for the GNU Emacs text editor
2022-01-13 5:54 ` ndame via Users list for the GNU Emacs text editor
2022-01-13 6:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-13 9:04 ` ndame via Users list for the GNU Emacs text editor [this message]
2022-01-19 20:47 ` ndame
2022-01-19 20:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-19 20:57 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-19 21:30 ` ndame
2022-01-19 23:44 ` Stefan Monnier via Users list for the GNU Emacs text editor
2022-01-20 4:47 ` ndame
2022-01-20 17:20 ` Stefan Monnier via Users list for the GNU Emacs text editor
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='FaMRsQQmJ1mIiI6CglfUiw4PQZciyHO7f8i9R06HQSYLByhHbb1_5XGedoNGWWGVm38359s84WjSO_yYvw27dyMlisOtAOjymTSkPk9INoc=@protonmail.com' \
--to=help-gnu-emacs@gnu.org \
--cc=laszlomail@protonmail.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.
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).