From: Jeff Horn <jrhorn424@gmail.com>
To: Nick Dokos <nicholas.dokos@hp.com>, emacs-orgmode@gnu.org
Subject: Re: Export LaTeX file to different directory?
Date: Mon, 13 Dec 2010 13:13:58 -0500 [thread overview]
Message-ID: <AANLkTimwhttQkzbVq=N2WTq7aNNDRxMPv=Cr9fJVwTmp@mail.gmail.com> (raw)
In-Reply-To: <20101213171545.GD283@pc201.uni-germanistik.gwdg.de>
On Mon, Dec 13, 2010 at 12:15 PM, Joost Kremers
<joostkremers@fastmail.fm> wrote:
> i'm using org version 7.4, if that's relevant at all. the variable
> org-export-publishing-directory is defined in org-exp.el (with defvar and a
> FIXME...), but it's not used anywhere in a meaningful way, AFAICT.
That just made me think... what if you define an org publishing
project with an output directory of "~/tmp" or whatever, and then tell
org, within each file, that the file belongs to your tmp project? When
you publish using "the current project", it should do what you're
looking for.
The only problem I can forsee is that there is no hash-plus file
property that can define which project a file belongs to. Maybe in the
future? (nudge, nudge)
--
Jeffrey Horn
Graduate Lecturer and PhD Student in Economics
George Mason University
(704) 271-4797
jhorn@gmu.edu
jrhorn424@gmail.com
http://www.failuretorefrain.com/jeff/
next prev parent reply other threads:[~2010-12-13 18:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-13 10:47 Export LaTeX file to different directory? Joost Kremers
2010-12-13 11:07 ` suvayu ali
2010-12-13 11:34 ` Joost Kremers
2010-12-13 11:52 ` suvayu ali
2010-12-13 15:43 ` Joost Kremers
2010-12-13 17:20 ` suvayu ali
[not found] ` <15397.1292255865@gamaville.dokosmarshall.org>
2010-12-13 17:15 ` Joost Kremers
2010-12-13 18:13 ` Jeff Horn [this message]
2010-12-13 18:34 ` Richard Lawrence
2010-12-13 18:36 ` Jeff Horn
2010-12-14 4:14 ` Richard Lawrence
2010-12-14 9:11 ` Joost Kremers
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='AANLkTimwhttQkzbVq=N2WTq7aNNDRxMPv=Cr9fJVwTmp@mail.gmail.com' \
--to=jrhorn424@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.