emacs-bug-tracker
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[debbugs-tracker] bug#16526: closed (24.3.50; scroll-conservatively & c-


From: GNU bug Tracking System
Subject: [debbugs-tracker] bug#16526: closed (24.3.50; scroll-conservatively & c-mode regression)
Date: Sun, 22 Jun 2014 16:50:02 +0000

Your message dated Sun, 22 Jun 2014 19:49:29 +0300
with message-id <address@hidden>
and subject line Re: bug#16526: 24.3.50; scroll-conservatively & c-mode 
regression
has caused the debbugs.gnu.org bug report #16526,
regarding 24.3.50; scroll-conservatively & c-mode regression
to be marked as done.

(If you believe you have received this mail in error, please contact
address@hidden)


-- 
16526: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16526
GNU Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: 24.3.50; scroll-conservatively & c-mode regression Date: Thu, 23 Jan 2014 09:53:17 +0100
With current trunk and emacs -Q evaluating the following form takes more
than two minutes here with builds on Windows and GNU/Linux:

(progn
  (setq scroll-conservatively 101)
  (find-file (concat source-directory "src/xdisp.c"))
  (end-of-buffer)
  (sit-for 3)
  (beginning-of-buffer))

It used to take about 10 seconds before revision 116070.

martin



--- End Message ---
--- Begin Message --- Subject: Re: bug#16526: 24.3.50; scroll-conservatively & c-mode regression Date: Sun, 22 Jun 2014 19:49:29 +0300
> Date: Thu, 06 Feb 2014 08:01:32 +0200
> From: Eli Zaretskii <address@hidden>
> Cc: address@hidden, address@hidden
> 
> > Date: Wed, 5 Feb 2014 23:00:01 +0000
> > Cc: address@hidden, address@hidden
> > From: Alan Mackenzie <address@hidden>
> > 
> > > Do you need help in identifying what takes 11 sec in the unoptimized
> > > build to traverse a few lines?
> > 
> > Thanks for the offer.  I really need to get down and spend a few hours
> > investigating.  I've elp'd CC Mode, and tried M-> (2 seconds) followed
> > by <PgUp> (13 seconds), and it looks like
> > c-append-lower-brace-pair-to-state-cache is taking up the time.  It
> > seems it is being called too often.  Maybe.
> > 
> > Maybe I'll pin it down at the weekend.
> 
> Thanks.

I hope Alan did something with this issue, or will in some near
future.

But either way, the original bug was fixed, so I'm closing this.


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]