emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: KDr2 <killy.draw@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+INCLUDE: file in code block results does not work?
Date: Wed, 26 Mar 2014 22:04:44 +0800	[thread overview]
Message-ID: <CAHfjm6g7CSfoM_4YL7+hKoqSN_WW+q+Zdx9c=HTj_1P2Km9D9Q@mail.gmail.com> (raw)
In-Reply-To: <CAHfjm6hSb=GGd1D6=NaR8iZKkShGozXVtte4k94d0A+o5tvCRQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 840 bytes --]

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


On Wed, Mar 26, 2014 at 7:54 PM, KDr2 <killy.draw@gmail.com> wrote:

> Thanks very much.
>
> I use dynamic block now, by adding `org-update-all-dblocks' to
> `org-export-before-processing-hook'.
>
>
> On Wed, Mar 26, 2014 at 5:42 PM, Nicolas Goaziou <n.goaziou@gmail.com>wrote:
>
>> Nicolas Goaziou <n.goaziou@gmail.com> writes:
>>
>> > You can use a macro here:
>> >
>> >   #+MACRO: inc-file #+INCLUDE: /path/to-include-dir/$1
>> >
>> >   {{{inc-file(a.org)}}}
>>
>> Err, no. Macros are also expanded after INCLUDE keywords. The only code
>> executed before these are handled is
>> `org-export-before-processing-hook'.
>>
>
>
>
> --
> --
>
> KDr2, http://kdr2.com
>



-- 
-- 

KDr2, http://kdr2.com

[-- Attachment #2: Type: text/html, Size: 2267 bytes --]

  reply	other threads:[~2014-03-26 14:05 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 [this message]
2014-03-26 14:31         ` Nicolas Goaziou
2014-03-26 14:38           ` KDr2

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='CAHfjm6g7CSfoM_4YL7+hKoqSN_WW+q+Zdx9c=HTj_1P2Km9D9Q@mail.gmail.com' \
    --to=killy.draw@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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).