From: Alan Mackenzie <acm@muc.de>
To: Tadeus Prastowo <tadeus.prastowo@unitn.it>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
emacs-devel <emacs-devel@gnu.org>
Subject: Re: Processing speed in large C++ raw strings.
Date: Sat, 27 Apr 2019 17:29:49 +0000 [thread overview]
Message-ID: <20190427172949.GC4822@ACM> (raw)
In-Reply-To: <CAN-HRFb3V4iUHPa5mwVZozxzYS0or4Rmrp88Un3oUv8zJLZb8w@mail.gmail.com>
Hello again, Tadeus.
On Sat, Apr 27, 2019 at 17:35:16 +0200, Tadeus Prastowo wrote:
> Hi Alan,
> On Sat, Apr 27, 2019 at 1:37 PM Alan Mackenzie <acm@muc.de> wrote:
> > Thanks for drawing my attention to this problem with lots of templates.
> My pleasure. And, thank you very much for looking into this.
> > The bug is that, in a certain low-level place, CC Mode was failing to
> > mark the < and > "as parentheses" (with syntax-table text properties),
> > hence a lot of unneeded buffer scanning was being done.
> > The following patch should speed up the scrolling operation markedly.
> > It does not become instantaneous, but takes a fraction of a second,
> > compared with the several seconds it has taken up to now. Would you
> > please try it out.
> I apply the following patch to master at commit
> 8dc00b2f1e6523c634df3e24379afbe712a32b27, and I confirm that the
> following patch works to solve not only the buffer scrolling
> sluggishness but also the template parameter editing sluggishness,
> including the one that I sent to Stefan earlier today. Thank you very
> much, Alan, I really appreciate it. Three lines of a diff to solve my
> two-year old sluggishness problem.
Thanks indeed! Thanks also for such a rapid reply.
I've just committed the patch to all the usual places (including the
Emacs master branch). So I think the bug is now fixed.
> > diff -r 1940f96b9799 cc-engine.el
> > --- a/cc-engine.el Fri Apr 26 01:01:07 2019 +0000
> > +++ b/cc-engine.el Sat Apr 27 11:30:06 2019 +0000
> > @@ -5539,7 +5539,9 @@
> > (prog1 (looking-at "\\s(")
> > (forward-char))))
> > (backward-char)
> > - (if (c-forward-<>-arglist nil) ; Should always work.
> > + (if (let ((c-parse-and-markup-<>-arglists t)
> > + (c-restricted-<>-arglists t))
> > + (c-forward-<>-arglist nil)) ; Should always work.
> > (when (> (point) to)
> > (setq bound-<> (point)))
> > (forward-char)))
> --
> Best regards,
> Tadeus
--
Alan Mackenzie (Nuremberg, Germany).
next prev parent reply other threads:[~2019-04-27 17:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 18:36 Processing speed in large C++ raw strings Alan Mackenzie
2019-04-26 1:25 ` Dmitry Gutov
2019-04-26 20:15 ` Tadeus Prastowo
2019-04-27 2:15 ` Stefan Monnier
2019-04-27 10:37 ` Tadeus Prastowo
2019-04-27 11:37 ` Alan Mackenzie
2019-04-27 15:35 ` Tadeus Prastowo
2019-04-27 17:29 ` Alan Mackenzie [this message]
2019-04-30 14:44 ` Tadeus Prastowo
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=20190427172949.GC4822@ACM \
--to=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=tadeus.prastowo@unitn.it \
/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).