From: andrei.elkin--- via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70495@debbugs.gnu.org
Subject: bug#70495: 29.3.50; M-x lsp leads to assertion failed: pdl->kind == SPECPDL_BACKTRACE
Date: Sun, 21 Apr 2024 16:43:34 +0300 [thread overview]
Message-ID: <87ttjubzll.fsf@quad> (raw)
In-Reply-To: <86r0ey7tcw.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 21 Apr 2024 16:11:59 +0300")
That's awesome Eli!
>> Cc: 70495@debbugs.gnu.org
>> Date: Sun, 21 Apr 2024 14:33:39 +0300
>> From: Eli Zaretskii <eliz@gnu.org>
>>
>> > Cc: 70495@debbugs.gnu.org
>> > Date: Sun, 21 Apr 2024 13:52:30 +0300
>> > From: Eli Zaretskii <eliz@gnu.org>
>> >
>> > Sorry, I cannot afford installing lsp-mode and lsp-ui (which in this
>> > case will need to also install clang for the LSP server, right?), and
>> > I don't know how to use it anyway. So I need you to tell me what's in
>> > the buffer at that position when this happens: how does
>> > lsp-mode/lsp-ui set the line-prefix or wrap-prefix, etc. If you can
>> > come up with a Lisp recipe that doesn't need lsp-* to be installed and
>> > still reproduces the problem, this would be the best, as I could debug
>> > this on my machine.
>>
>> Never mind, I've succeeded in reproducing this on my system. No lsp-*
>> packages are needed at all, it's very simple to reproduce.
>>
>> Stay tuned.
>
> FTR: to reproduce the problem, it's enough to evaluate this in "emacs -Q":
>
> (setq line-prefix '(space :width 1))
>
> I guess no one tried to do this since Emacs 29 was released...
>
> Anyway, should be fixed now on the emacs-29 branch.
Thank you!
Andrei
PS. I'll reconsider -O3 - was not aware of its fragility.
next prev parent reply other threads:[~2024-04-21 13:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-21 9:41 bug#70495: 29.3.50; M-x lsp leads to assertion failed: pdl->kind == SPECPDL_BACKTRACE andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-04-21 10:52 ` Eli Zaretskii
2024-04-21 11:33 ` Eli Zaretskii
2024-04-21 13:11 ` Eli Zaretskii
2024-04-21 13:43 ` andrei.elkin--- via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2024-05-02 8:44 ` Eli Zaretskii
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=87ttjubzll.fsf@quad \
--to=bug-gnu-emacs@gnu.org \
--cc=70495@debbugs.gnu.org \
--cc=andrei.elkin@pp.inet.fi \
--cc=eliz@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.
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).