Nicolas Goaziou wrote:
> Eli Zaretskii writes:
>
>> Thanks. So this looks like a problem with Org Mode. In particular,
>> org-element-inline-babel-call-successor takes a lot of time in this
>> case. That function traverses the buffer from top to bottom:
>>
>> (while (search-forward "call_
> So, it only covers a single command (C-k).
Sorry, forget my question: I had forgotten to turn my brain on, somehow
(seems to happen too often lately).
These numbers aren't call counts, they're just numbers of samples, so
there's no evidence that flyspell-post-command-hook was run very many times
Stefan wrote:
>> I thought at using the profiler of Emacs 24, and it gives meaningful
>> results. Good news #2.
>> Here they are:
>> --8<---cut here---start->8---
>> - flyspell-post-command-hook 3271 98%
>
> Does this report o
> I thought at using the profiler of Emacs 24, and it gives meaningful
> results. Good news #2.
> Here they are:
> --8<---cut here---start->8---
> - flyspell-post-command-hook 3271 98%
Does this report only cover a single com
Eli Zaretskii writes:
> Do you happen to know, or can measure, how much faster is the latest
> version? Given the timing provided by the OP, it'd have to be at
> least 100 times faster, to avoid annoying delays after each command.
Basically it is,
(search-forward "call_")
versus
(re-sear
> From: Nicolas Goaziou
> Cc: Fabrice Niessen , emacs-orgmode@gnu.org,
> 16...@debbugs.gnu.org
> Date: Sat, 15 Mar 2014 17:17:26 +0100
>
> > (while (search-forward "call_" nil t)
> > (save-excursion
> > (goto-char (match-beginning 0))
> > (when (looking-at org-babel-inlin
Hello,
Eli Zaretskii writes:
> Thanks. So this looks like a problem with Org Mode. In particular,
> org-element-inline-babel-call-successor takes a lot of time in this
> case. That function traverses the buffer from top to bottom:
>
> (while (search-forward "call_" nil t)
> (save-
> From: Fabrice Niessen
> Cc: 16...@debbugs.gnu.org, emacs-orgmode
> Date: Fri, 14 Mar 2014 17:00:54 +0100
>
> I realized that Emacs did not into an infloop, but simply gave me back
> control after a very long time (more than 2 mins). Good news #1.
>
> I thought at using the profiler of Emacs 2
Eli Zaretskii wrote:
>> From: "Fabrice Niessen"
>> Cc: 16...@debbugs.gnu.org
>> Date: Wed, 26 Feb 2014 20:42:20 +0100
>>
>> Eli Zaretskii wrote:
>> >> From: "Fabrice Niessen"
>> >> Cc: 16...@debbugs.gnu.org
>> >> Date: Wed, 26 Feb 2014 12:06:24 +0100
>> >>
>> >> > Then try F12 (if you are on XP
