From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Open all #+INCLUDED:d files?
Date: Fri, 12 Dec 2014 12:35:59 -0500 [thread overview]
Message-ID: <87oar8epog.fsf@alphaville.usersys.redhat.com> (raw)
In-Reply-To: m2k31xayg3.fsf@krugs.de
Rainer M Krug <Rainer@krugs.de> writes:
> Rasmus <rasmus@gmx.us> writes:
>
>> Rainer M Krug <Rainer@krugs.de> 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 should be easy with org-element-map. Map over all
>> keywords, ensure they are INCLUDE keywords, move point to their :begin
>> and call org-edit-special or similar. You could use save-excursion,
>> save-window-excursion to make it not suck. You'd might have to widen
>> first, then you could use save-restriction.
>
> OK - I might look into it when I get to annoyed by the manual approach.
>
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 deleted it but that's not surpising: it
probably went away when the new exporter came in.
It should be possible to add a similar function (based on element
mapping as Rasmus suggests).
There is also a function in org-hacks on Worg that did what you
are trying to do, but since it was based on the above, it no longer
works:
http://orgmode.org/worg/org-hacks.html#sec-1-10-2
That section needs to be marked obsolete (or taken out altogether).
Nick
next prev parent reply other threads:[~2014-12-12 17:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 9:08 Open all #+INCLUDED:d files? Rainer M Krug
2014-12-12 11:14 ` Rasmus
2014-12-12 11:19 ` Rasmus
2014-12-12 11:40 ` Rainer M Krug
2014-12-12 17:35 ` Nick Dokos [this message]
2014-12-12 18:07 ` Nicolas Goaziou
2014-12-12 18:13 ` Rasmus
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87oar8epog.fsf@alphaville.usersys.redhat.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).