From: KDr2 <killy.draw@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+INCLUDE: file in code block results does not work?
Date: Wed, 26 Mar 2014 22:38:36 +0800 [thread overview]
Message-ID: <CAHfjm6jwgipnJeW+o5qD96Lphi99qsRh5_OPwm3sNU0y_SExrg@mail.gmail.com> (raw)
In-Reply-To: <878urxuj4g.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1175 bytes --]
Oh, I'll star this mail, and add it to my post later, thanks again :)
On Wed, Mar 26, 2014 at 10:31 PM, Nicolas Goaziou <n.goaziou@gmail.com>wrote:
> Hello,
>
> KDr2 <killy.draw@gmail.com> writes:
>
> > I wrote a blog entry to describe all the dynamic tricks I used in the
> > exporting:
> >
> > http://kdr2.com/tech/emacs/orgmode-export-process.html
>
> Thank you for sharing.
>
> For completeness, there is another step involved in the process before
> switching to back-ends: run functions in
> `org-export-before-parsing-hook'.
>
> >> I use dynamic block now, by adding `org-update-all-dblocks' to
> >> `org-export-before-processing-hook'.
>
> Also, you can also a function in the same hook that would update
> a generic "inc-file" macro in the file:
>
> (lambda (backend)
> (org-with-wide-buffer
> (goto-char (point-min))
> (let ((case-fold-search nil))
> (while (re-search-forward "^ *#\\+MACRO: +inc-file +\"\\(PATH\\)"
> nil t)
> (replace-match (get-path-dynamically) t nil nil 1)))))
>
> with the following generic macro:
>
> #+MACRO: inc-file "PATH$1"
>
>
> Regards,
>
> --
> Nicolas Goaziou
>
--
--
KDr2, http://kdr2.com
[-- Attachment #2: Type: text/html, Size: 2082 bytes --]
prev parent reply other threads:[~2014-03-26 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-26 7:48 #+INCLUDE: file in code block results does not work? KDr2
2014-03-26 9:35 ` Nicolas Goaziou
2014-03-26 9:42 ` Nicolas Goaziou
2014-03-26 11:54 ` KDr2
2014-03-26 14:04 ` KDr2
2014-03-26 14:31 ` Nicolas Goaziou
2014-03-26 14:38 ` KDr2 [this message]
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=CAHfjm6jwgipnJeW+o5qD96Lphi99qsRh5_OPwm3sNU0y_SExrg@mail.gmail.com \
--to=killy.draw@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).