From: Matt Price <firstname.lastname@example.org>
To: Matt Price <email@example.com>, Org Mode <firstname.lastname@example.org>
Subject: Re: set a location for simple export of individual file?
Date: Tue, 31 Mar 2015 09:12:13 -0400 [thread overview]
Message-ID: <CAN_Dec-S2-F4uujmr5k3qe5OR05dvTgfF5VUy_5JbFL-8BAEmg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1128 bytes --]
Wow, that was way easier than I thought it would be. Made a couple of
modest changes to org-html-to-html, and now a simple keybinding exports to
my desired location and opens the file in my desired location, which I
purge every couple of days. Thank you!
On Sat, Mar 28, 2015 at 11:43 AM, Nicolas Goaziou <email@example.com>
> Matt Price <firstname.lastname@example.org> writes:
> > I have an org file with lots of long tables in it; org is great for the
> > data entry part, but sometimes I want to see the long lines in the table
> > their entirety, and for this I export to HTML. It works great. However,
> > for whatever reason I don't want the HTML to live in the same directory
> > the original org file.*
> > I have tried this:
> > #+BIND: org-export-publishing-directory "/tmp/"
> > But that doesn't work, I think because I export using the export
> > not by publishing. Is there a comparable variable for export location?
> You can build a function around `org-export-to-file'. See
> `org-html-export-to-html' for example.
> Nicolas Goaziou
[-- Attachment #2: Type: text/html, Size: 1691 bytes --]
prev parent reply other threads:[~2015-03-31 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-28 14:11 Matt Price
2015-03-28 15:43 ` Nicolas Goaziou
2015-03-31 13:12 ` Matt Price [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).