From: Lars Ingebrigtsen <larsi@gnus.org>
To: Ryan Olson <ryan.olson.x@gmail.com>
Cc: 46713@debbugs.gnu.org
Subject: bug#46713: 27.1; Variable binding depth exceeds max-specpdl-size in js-mode with js-indent-level 2 and indent-tabs-mode nil on new line
Date: Tue, 23 Feb 2021 16:36:21 +0100 [thread overview]
Message-ID: <87ft1mdcei.fsf@gnus.org> (raw)
In-Reply-To: <CAKkY5K499zMp30P_qm4jPNGT+h=6_T3HAMO=yQV3Q+vs+CH27w@mail.gmail.com> (Ryan Olson's message of "Mon, 22 Feb 2021 19:03:39 -0700")
Ryan Olson <ryan.olson.x@gmail.com> writes:
> Repro steps:
> 1. Open foo.js with emacs -Q --eval '(setq-default js-indent-level 2
> indent-tabs-mode nil)' foo.js
> 2. Go to line 61
> 3. Delete brace at end of that line
> 4. Save
> 5. Add brace back
> 6. Press RET
> 7. Errors happen
Thanks for the clear recipe. With it, I'm also seeing errors (in both
Emacs 27 and 28):
Debugger entered--Lisp error: (error "internal--syntax-propertize did not move syntax-pr...")
backward-prefix-chars()
back-to-indentation()
current-left-margin()
move-to-left-margin(nil t)
#f(compiled-function () #<bytecode 0x155c01f42651>)()
self-insert-command(1)
newline(nil 1)
funcall-interactively(newline nil 1)
call-interactively(newline nil nil)
But I'm not seeing the "binding depth" one.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-02-23 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-22 22:22 bug#46713: 27.1; Variable binding depth exceeds max-specpdl-size in js-mode with js-indent-level 2 and indent-tabs-mode nil on new line Ryan Olson
2021-02-22 22:36 ` Lars Ingebrigtsen
2021-02-23 2:03 ` Ryan Olson
2021-02-23 15:36 ` Lars Ingebrigtsen [this message]
2021-02-23 16:31 ` Ryan Olson
2021-02-24 16:47 ` Lars Ingebrigtsen
2022-06-19 13:53 ` Lars Ingebrigtsen
2022-06-25 12:03 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-06-25 12:43 ` Lars Ingebrigtsen
2022-06-26 13:00 ` 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=87ft1mdcei.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=46713@debbugs.gnu.org \
--cc=ryan.olson.x@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).