Hi Richard, Richard G Riley <[EMAIL PROTECTED]> writes:
> Should the properties given here > > http://orgmode.org/manual/Publishing-options.html#Publishing-options > > be applicable in this form: > > ,---- > | #+TITLE: Blog > | #+AUTHOR: rgr > | #+EMAIL: rgr > | #+DATE: <2008-03-23 Sun> > | #+LANGUAGE: en > | #+TEXT: Test Blog > | > | :PROPERTIES: > | :publishing-directory: ~/webs/web1/public_html > | :table-of-contents: nil > | :END: > | > | * Blog You can set most of the options listed on this page by setting the proper flag on the #+OPTIONS: line. E.g. the table of contents: #+OPTIONS: toc:nil This is documented here: http://orgmode.org/manual/Export-options.html#Export-options The #+OPTIONS line is not a suitable place for setting the publishing directory, because the value for this is likely to be too long. For now, there is no other mean to set the publishing directory but to define a project or to set `org-export-publishing-directory' locally in the file. But I agree that a simple(r) way to set this would be nice. What about #+EXPORT_DIRECTORY ? (Instead of a property in :PROPERTIES:) Note: the export/publish semantic is a bit misleading here. The manual talks about export options and publishing options. Many export options are also publishing options, but not all publishing options are export options -- the most obvious example being the :recursive publishing option, which only makes sense for projects/directories. I will try to clarify this and to refactor the option names a bit. Thanks for bringing this up. > I can't seem to set the directory the html gets written to. But I > should be able to do it without using org-publish-project-alist ? As mentionned above, for now: * COMMENT Local variables # Local Variables: # org-export-publishing-directory: "~/public_html/" # End: -- Bastien _______________________________________________ Emacs-orgmode mailing list Remember: use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
