From: Nick Dokos <nicholas.dokos@hp.com>
To: Noufal Ibrahim <noufal@nibrahim.net.in>
Cc: emacs-orgmode@gnu.org
Subject: Re: Name of file being exported.
Date: Tue, 14 Apr 2009 12:20:14 -0400 [thread overview]
Message-ID: <16352.1239726014@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Noufal Ibrahim <noufal@nibrahim.net.in> of "Tue, 14 Apr 2009 20:28:44 +0530." <49E4A4A4.8050909@nibrahim.net.in>
Noufal Ibrahim <noufal@nibrahim.net.in> wrote:
> Carsten Dominik wrote:
> [..]
> > In what way are you calling the update of dblocks during export?
> > Have you added a function to this effect to a hook? Which function?
> > To which hook?
> [..]
>
> Hello Carsten,
> I have done this
> (add-hook 'org-export-preprocess-hook 'org-update-all-dblocks)
>
> Is this not the right hook to add the function to?
>
I don't know how Carsten will address this, but it seems that the running
of the org-export-preprocess-hook is done too late for your purposes (from
inside org-export-preprocess-string and inside a
(with-current-buffer (get-buffer-create " org-mode-tmp")
...
construct, where there is no buffer file name).
Can you run org-update-all-dblocks by hand before doing the export? That should
update the org file and the export should then have all the right
information, no? If so, you can even automate the process by advising
org-export, so that org-update-all-dblocks is run before org-export
proper is called. [1]
HTH,
Nick
[1] Disclaimer: I have not tried it, so no warranty...
next prev parent reply other threads:[~2009-04-14 16:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 2:22 Name of file being exported Noufal Ibrahim
2009-04-14 10:32 ` Carsten Dominik
2009-04-14 14:58 ` Noufal Ibrahim
2009-04-14 16:20 ` Nick Dokos [this message]
2009-04-14 16:39 ` Noufal Ibrahim
2009-04-14 18:26 ` Nick Dokos
2009-04-15 5:02 ` Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2009-04-13 21:33 Noufal Ibrahim
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=16352.1239726014@gamaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=noufal@nibrahim.net.in \
/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).