From: ndame <laszlomail@protonmail.com>
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: Wed, 19 Jan 2022 20:47:38 +0000 [thread overview]
Message-ID: <nY2Zo90KD4pUvLR39E4aDs_yM1kp46FfdqEXG4aCeh1mrBtzGPd57kj2jOUMqtcRQwQAH--ub-Iiik1XOVtq40dj6_MI6cY5MYcRCezF3k8=@protonmail.com> (raw)
In-Reply-To: <FaMRsQQmJ1mIiI6CglfUiw4PQZciyHO7f8i9R06HQSYLByhHbb1_5XGedoNGWWGVm38359s84WjSO_yYvw27dyMlisOtAOjymTSkPk9INoc=@protonmail.com>
>
> 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.
The maintainer is not really responsive. I skimmed the code and
it seems it only calls (indent-according-to-mode) and stuff,
and does not do anything crazy:
https://github.com/Malabarba/aggressive-indent-mode/blob/master/aggressive-indent.el
Would you agree that if the code does only automatic indentation
for the user by calling core indent functions then it's likely
that emacs is the culprit for the error and I should submit
a bug report for emacs?
The problem is reproducible and it only requires installing
aggressive-indent-mode which is in GNU ELPA.
next prev parent reply other threads:[~2022-01-19 20:47 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
2022-01-19 20:47 ` ndame [this message]
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='nY2Zo90KD4pUvLR39E4aDs_yM1kp46FfdqEXG4aCeh1mrBtzGPd57kj2jOUMqtcRQwQAH--ub-Iiik1XOVtq40dj6_MI6cY5MYcRCezF3k8=@protonmail.com' \
--to=laszlomail@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).