From: Julien Cubizolles <j.cubizolles@free.fr>
To: emacs-orgmode@gnu.org
Subject: Re: Using Buffer name in :include export property
Date: Fri, 29 Aug 2014 11:40:07 +0200 [thread overview]
Message-ID: <87k35reirs.fsf@free.fr> (raw)
In-Reply-To: 871ts0yzdq.fsf@alphaville.bos.redhat.com
Nick Dokos <ndokos@gmail.com> writes:
> Julien Cubizolles <j.cubizolles@free.fr> writes:
>
>> I'm using the following elisp source block in my org files to choose the
>> publication options.
>>
>> (setq org-publish-project-alist
>> '(("TeX"
>> :base-directory "./"
>> :publishing-directory "./"
>> :publishing-function org-beamer-publish-to-latex
>> :exclude ".*"
>> :latex-class "mpsi_beamer"
>> :include ("test.org"))
>> ))
>>
>> I'd like to define it once and for all in my emacs
>> configuration files but I'd need to replace the
>>
>> :include ("test.org")
>>
>> line with the result of (buffer-name). Is it possible ?
>>
>
> Do you mean buffer-file-name?
Yes that's better.
> When you publish a project, it does not matter what your current buffer
> is. So why would you want to include the random file that you just
> happen to be visiting? And what if the buffer is not associated with a
> file at all (so buffer-file-name returns nil)?
> Can you explain what exactly you are trying to do?
I need to export the same org file with different latex classes and
package options. I do so by using different projects for the same file.
> The usual method of splicing in a variable into a list is with
> backquote - see e.g.
>
> http://thread.gmane.org/gmane.emacs.orgmode/9583/focus=9603
>
> but I don't think that would work here in any case.
Thanks for the pointer, it works:
--8<---------------cut here---------------start------------->8---
(defun jc-org-publish-project-options ()
(setq org-publish-project-alist
`(("TeX"
:base-directory "./"
:publishing-directory "./"
:publishing-function org-beamer-publish-to-latex
:exclude ".*"
:latex-class "mpsi_beamer"
:include , (list (file-name-nondirectory buffer-file-name))
)
( several other projects...)
)))
(add-hook 'org-mode-hook 'jc-org-publish-project-options)
(add-hook 'org-export-before-processing-hook 'jc-org-publish-project-options)
--8<---------------cut here---------------end--------------->8---
I'm not sure file-name-nondirectory is necessary. As you can see I need
to hook this function twice:
- the org-mode-hook is so that the project names are available in any
org file
- the org-export-before-processing-hook is to adapt the :include option
to each org file before export.
That's not very elegant, if someone has any idea.
Julien.
next prev parent reply other threads:[~2014-08-29 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-28 21:37 Using Buffer name in :include export property Julien Cubizolles
2014-08-28 23:21 ` Nick Dokos
2014-08-29 9:40 ` Julien Cubizolles [this message]
2014-08-29 10:34 ` Julien Cubizolles
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=87k35reirs.fsf@free.fr \
--to=j.cubizolles@free.fr \
--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).