From: Lars Ingebrigtsen <larsi@gnus.org>
To: Alan Mackenzie <acm@muc.de>
Cc: 33670@debbugs.gnu.org, Chris Hecker <checker@d6.com>
Subject: bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64
Date: Mon, 28 Feb 2022 10:53:06 +0100 [thread overview]
Message-ID: <87ilszpbb1.fsf@gnus.org> (raw)
In-Reply-To: <YfVsxbPEk4cgGXXI@ACM> (Alan Mackenzie's message of "Sat, 29 Jan 2022 16:35:17 +0000")
Alan Mackenzie <acm@muc.de> writes:
> I suspect the bug, whatever it was, will have been fixed since late
> 2018. The raw string processing has been significantly enhanced since
> then.
>
> So, Chris, are the problems still apparent?
More information was requested, but no response was given within a
month, so I'm closing this bug report. If the problem still exists,
please respond to this email and we'll reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-28 9:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-08 2:42 bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64 Chris Hecker
2018-12-08 2:56 ` bug#33670: adding some info to my yank perf regression Chris Hecker
2018-12-08 7:49 ` bug#33670: 26.1; very large c++-mode yank performance regression 25.3_1-x86_64 -> 26.1-x86_64 Eli Zaretskii
[not found] ` <mailman.5359.1544236991.1284.bug-gnu-emacs@gnu.org>
2018-12-08 20:40 ` Alan Mackenzie
2018-12-08 21:31 ` Chris Hecker
2018-12-09 12:01 ` Alan Mackenzie
2018-12-09 17:57 ` Chris Hecker
2018-12-09 18:26 ` Alan Mackenzie
2022-01-29 15:20 ` Lars Ingebrigtsen
2022-01-29 16:35 ` Alan Mackenzie
2022-02-28 9:53 ` Lars Ingebrigtsen [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ilszpbb1.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=33670@debbugs.gnu.org \
--cc=acm@muc.de \
--cc=checker@d6.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.