From: Lars Ingebrigtsen <larsi@gnus.org>
To: Paul Nelson <ultrono@gmail.com>
Cc: Alan Mackenzie <acm@muc.de>, 48100@debbugs.gnu.org
Subject: bug#48100: 28.0.50; inserting too many lines into a fresh cpp file breaks the buffer
Date: Sun, 02 May 2021 09:58:26 +0200 [thread overview]
Message-ID: <874kflk1nh.fsf@gnus.org> (raw)
In-Reply-To: <CAOA-32PSKEQC8mzO64KGWu-Og+AF6zWTtCgO-gjes5CnvNHaiQ@mail.gmail.com> (Paul Nelson's message of "Thu, 29 Apr 2021 10:04:36 +0200")
Paul Nelson <ultrono@gmail.com> writes:
> Start from emacs -Q. Insert sufficiently many lines of C++ code in a
> temporary buffer. A slightly contrived example:
[...]
> Copy these lines to the kill ring. Create a new file "test.cpp", and
> paste what was copied.
>
> The first error is that syntax highlighting stops after a certain
> number of lines (in the above example, just before the final line).
I tried this in Emacs 28, and I could not reproduce the reported
behaviour -- this works fine for me.
> Incidentally, "C-u C-M-x" applied to c-guess-basic-syntax gives a long and
> complicated backtrace that starts with:
>
> Debugger entered--Lisp error: (invalid-read-syntax "Expected" "lambda")
> edebug-syntax-error("Expected" "lambda")
I can reproduce this, though, so I've added Alan to the CCs.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-05-02 7:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-29 8:04 bug#48100: 28.0.50; inserting too many lines into a fresh cpp file breaks the buffer Paul Nelson
2021-05-02 7:58 ` Lars Ingebrigtsen [this message]
2021-05-02 12:24 ` Alan Mackenzie
2021-05-02 13:33 ` Basil L. Contovounesios
2021-05-02 15:01 ` Alan Mackenzie
2021-05-05 3:01 ` Paul Nelson
2021-05-05 9:26 ` Lars Ingebrigtsen
2021-05-05 10:18 ` Alan Mackenzie
2021-05-06 10:26 ` Paul Nelson
2021-05-09 9:33 ` Alan Mackenzie
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=874kflk1nh.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=48100@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=ultrono@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).