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 14:26:50 -0400 [thread overview]
Message-ID: <17069.1239733610@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Noufal Ibrahim <noufal@nibrahim.net.in> of "Tue, 14 Apr 2009 22:09:48 +0530." <49E4BC54.1060504@nibrahim.net.in>
Noufal Ibrahim <noufal@nibrahim.net.in> wrote:
> Hi Nick,
>
> Nick Dokos wrote:
> [..]
> >
> > Can you run org-update-all-dblocks by hand before doing the export?
>
> That's possible. What I do now is to to add the
> org-update-all-dbblocks to write-file-hooks as suggested by the info
> pages.
>
> This works for me but there are times when I export directly without
> saving and I'd like the block to get updated then too.
>
> > 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]
>
> This sounds better. I shall try this. Although I'm wondering if there
> isn't a hook that I can add a function to manage what I want.
>
Maybe this will work: the current buffer-file-name is saved in
org-export-as-html (and I assume in the other export routines) in a
dynamically scoped variable called org-current-export-file. The value of
that variable should be available in the hook as well. So instead of
(buffer-file-name), you probably want to say
(or (buffer-file-name) org-current-export-file)
That way, your updater can be called both from inside and outside
the export functions.
HTH,
Nick
next prev parent reply other threads:[~2009-04-14 18:28 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
2009-04-14 16:39 ` Noufal Ibrahim
2009-04-14 18:26 ` Nick Dokos [this message]
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=17069.1239733610@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).