* third export request
@ 2006-05-19 20:22 Austin Frank
2006-05-20 11:06 ` Carsten Dominik
0 siblings, 1 reply; 3+ messages in thread
From: Austin Frank @ 2006-05-19 20:22 UTC (permalink / raw)
To: emacs-orgmode
Last one on this topic, I think :)
I don't know if this is more of an org-export or an org-publish request,
but I'd like to be able to do something like
(setq org-export-as-ascii-directory "~/notes/text/")
and have any org-export-as-ascii files sent to that directory. Likewise
for the other org-export-as-* functions. It'd be nice to be able to
configure where the ical files end up when they're exported, as well.
Allowing exports to be written to specific directories seems like it
might provide a sensible default for the :publishing-directory plist
entry in org-publish-projects-alist, but I admit I haven't thought that
through very thoroughly.
Thanks again for reading,
/au
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: third export request
2006-05-19 20:22 third export request Austin Frank
@ 2006-05-20 11:06 ` Carsten Dominik
2006-05-21 15:02 ` Austin Frank
0 siblings, 1 reply; 3+ messages in thread
From: Carsten Dominik @ 2006-05-20 11:06 UTC (permalink / raw)
To: Austin Frank; +Cc: emacs-orgmode
This is no problem. I will probably not make separate variables for
this, but allow an alist value for org-publishing-directory that can
look like this:
(setq org-publishing-directory
'((:html . "./html/")
(:ascii . "../text/")
(:xoxo . "html/")))
Something along those lines.
I have too many publishing options already - I should have done this
with property lists from the beginning, but unfortunately did not think
of this possibility. Sort of too late now.
- Carsten
On May 19, 2006, at 22:22, Austin Frank wrote:
> Last one on this topic, I think :)
>
> I don't know if this is more of an org-export or an org-publish
> request, but I'd like to be able to do something like
>
> (setq org-export-as-ascii-directory "~/notes/text/")
>
> and have any org-export-as-ascii files sent to that directory.
> Likewise for the other org-export-as-* functions. It'd be nice to be
> able to configure where the ical files end up when they're exported,
> as well.
>
> Allowing exports to be written to specific directories seems like it
> might provide a sensible default for the :publishing-directory plist
> entry in org-publish-projects-alist, but I admit I haven't thought
> that through very thoroughly.
>
> Thanks again for reading,
> /au
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
>
>
--
Carsten Dominik
Sterrenkundig Instituut "Anton Pannekoek"
Universiteit van Amsterdam
Kruislaan 403
NL-1098SJ Amsterdam
phone: +31 20 525 7477
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: third export request
2006-05-20 11:06 ` Carsten Dominik
@ 2006-05-21 15:02 ` Austin Frank
0 siblings, 0 replies; 3+ messages in thread
From: Austin Frank @ 2006-05-21 15:02 UTC (permalink / raw)
To: Carsten Dominik; +Cc: emacs-orgmode
Carsten Dominik wrote:
> This is no problem. I will probably not make separate variables for
> this, but allow an alist value for org-publishing-directory that can
> look like this:
>
>
> (setq org-publishing-directory
> '((:html . "./html/")
> (:ascii . "../text/")
> (:xoxo . "html/")))
>
> Something along those lines.
This looks good. Will ical be included in the same alist even though it
is not an org-export-as-* function? If not, will there be a way to set
an export directory for icalendar-export-* ?
Thanks,
/au
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2006-05-21 15:02 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2006-05-19 20:22 third export request Austin Frank
2006-05-20 11:06 ` Carsten Dominik
2006-05-21 15:02 ` Austin Frank
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).