Glenn Morris <r...@gnu.org> writes:

> "Sebastien Vauban" wrote:
>
>> But I wonder: how can you now reproduce it (and not before)?
>
> Because I downloaded a snapshot of Org.
> Your problem is not with code that is in Emacs current trunk.

Using Glenn's reproducer, I bisected it - another one for Nicolas's
TODO list, proving once again that no good deed goes unpunished :-)

0cecf32a0ae559266555b96668dc305710366c96 is the first bad commit
commit 0cecf32a0ae559266555b96668dc305710366c96
Author: Nicolas Goaziou <n.goaz...@gmail.com>
Date:   Sun Oct 27 11:09:17 2013 +0100

    org-element: Implement caching for dynamic parser
    
    * lisp/org-element.el (org-element-use-cache, org-element--cache,
    org-element--cache-sync-idle-time,
    org-element--cache-merge-changes-threshold, org-element--cache-status,
    org-element--cache-opening-line, org-element--cache-closing-line): New
    variables.
    (org-element-cache-reset, org-element--cache-pending-changes-p,
    org-element--cache-push-change, org-element--cache-cancel-changes,
    org-element--cache-get-key, org-element-cache-get,
    org-element-cache-put, org-element--shift-positions,
    org-element--cache-before-change, org-element--cache-record-change,
    org-element--cache-sync): New functions.
    (org-element-at-point, org-element-context): Use cache when possible.
    * lisp/org.el (org-mode, org-set-modules): Reset cache.
    * lisp/org-footnote.el (org-footnote-section): Reset cache.
    * testing/lisp/test-org-element.el: Update tests.
    
    This patch gives a boost to `org-element-at-point' and, to a lesser
    extent, to `org-element-context'.

:040000 040000 d1c8eb78998a7fd1266ff2fb2748842dba4ea3b9 
d7f65666fe694ec51132833e45061a38d1a1bb3f M      lisp
:040000 040000 ed2b1f509358abd49f10431abb6b933ae4c505de 
fa669197f78a08839d14a35f4906826c69233626 M      testing


Reply via email to