Nicolas Goaziou writes:
> Hello,
>
> Nick Dokos writes:
>
>> The old exporter provided a function,
>> org-export-handle-include-files-recurse,
>> that allowed an org-to-org export, recursively including the files. The
>> commit that introduced it was
>>
>>5633f7084a96298f415f07c348844bd5f22
Hello,
Nick Dokos writes:
> The old exporter provided a function, org-export-handle-include-files-recurse,
> that allowed an org-to-org export, recursively including the files. The
> commit that introduced it was
>
>5633f7084a96298f415f07c348844bd5f22eb81e
>
> I didn't find a commit that del
Rainer M Krug writes:
> Rasmus writes:
>
>> Rainer M Krug writes:
>>
>>> Is there an easy way of opening all INCLUDEd files in an org document,
>>> i.e. a single command or an easy way of doing it via some elisp code?
>>
>> Oh, sorry, I didn't see the "all".
>
> No problem - so I learned about
Rasmus writes:
> Rainer M Krug writes:
>
>> Is there an easy way of opening all INCLUDEd files in an org document,
>> i.e. a single command or an easy way of doing it via some elisp code?
>
> Oh, sorry, I didn't see the "all".
No problem - so I learned about C-c & - very useful.
> But yeah, it
Rainer M Krug writes:
> Is there an easy way of opening all INCLUDEd files in an org document,
> i.e. a single command or an easy way of doing it via some elisp code?
Oh, sorry, I didn't see the "all". But yeah, it should be easy with
org-element-map. Map over all keywords, ensure they are INC
Hi,
Rainer M Krug writes:
> Is there an easy way of opening all INCLUDEd files in an org document,
> i.e. a single command or an easy way of doing it via some elisp code?
C-c ' and C-c & to return.
It even works on this link:
#+INCLUDE: "/tmp/t1.org::*foo"
For how to do it lisp look at how
Hi
Is there an easy way of opening all INCLUDEd files in an org document,
i.e. a single command or an easy way of doing it via some elisp code?
Thanks,
Rainer
--
Rainer M. Krug
email: Rainerkrugsde
PGP: 0x0F52F982
signature.asc
Description: PGP signature
