Hi,
ยท Myles English <mylesengl...@gmail.com> wrote:
[ ... snip ... ]
> It was possible to insert a link to an attachment like this:
>
> [[att:FigureA.jpg]]
>
> and clicking on it would show the file (still works), and it would show
> up in the exported document (no longer happens).
[ ... snip ... ]
since I like this feature I'd like to give this thread a bump. With git
bisecting I found that commit:
026b99ecb86e08f4fdc7b45ee2bfa1d4c84a37f6 is the first bad commit
commit 026b99ecb86e08f4fdc7b45ee2bfa1d4c84a37f6
Author: Nicolas Goaziou <n.goaz...@gmail.com>
Date: Fri Aug 30 13:29:51 2013 +0200
org-element: Fix parsing error in `org-element-context'
* lisp/org-element.el (org-element-text-markup-successor,
org-element-latex-or-entity-successor,
org-element-export-snippet-successor,
org-element-footnote-reference-successor,
org-element-inline-babel-call-successor,
org-element-inline-src-block-successor,
org-element-line-break-successor, org-element-link-successor,
org-element-plain-link-successor, org-element-macro-successor,
org-element-radio-target-successor,
org-element-statistics-cookie-successor,
org-element-sub/superscript-successor,
org-element-table-cell-successor, org-element-target-successor,
org-element-timestamp-successor): Remove LIMIT argument.
(org-element--parse-objects, org-element--get-next-object-candidates):
Apply signature change to successors.
(org-element-context): Narrow buffer around object containers so
parsing of objects when using this function is done under the same
restrictions as in buffer parsing.
* testing/lisp/test-org-element.el: Add test.
introduced the bug. Now my elisp knowledge is too weak to debug this
further, but hopefully this helps to trace down the root cause.
Thanks a lot for org. I really don't know how to survive without it :-)
--
Bis neulich ...
Thomas
