From mboxrd@z Thu Jan 1 00:00:00 1970 From: Richard Lawrence Subject: Re: Publish project alist in org-mode 8 - confusing documentation Date: Thu, 06 Mar 2014 12:56:10 -0800 Message-ID: <87k3c7vyfp.fsf@berkeley.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:51031) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLfMu-0007MG-KE for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 15:58:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WLfMj-0004ue-0n for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 15:58:16 -0500 Received: from plane.gmane.org ([80.91.229.3]:55293) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WLfMi-0004uR-Qm for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 15:58:04 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1WLfMf-0004cQ-1D for emacs-orgmode@gnu.org; Thu, 06 Mar 2014 21:58:01 +0100 Received: from c-67-164-45-159.hsd1.ca.comcast.net ([67.164.45.159]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Mar 2014 21:58:01 +0100 Received: from richard.lawrence by c-67-164-45-159.hsd1.ca.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 06 Mar 2014 21:58:01 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Cc: suleika@gmail.com Hi Gez, Gez writes: > but I don't know where to begin adapting it to the new export framework. > > For example, I'd be very grateful if someone could "translate" the > following (or something more simple) into org-mode 8 version, so I can > start evaluating and playing with it. > > (require 'org-publish) > (setq org-publish-project-alist > '( > ("org-notes" > :base-directory "~/org/" > :base-extension "org" > :publishing-directory "~/public_html/" > :recursive t > :publishing-function org-publish-org-to-html It's been a while since I converted my publishing setup to the new exporter, but I *think* the only change you need to make here is to the :publishing-function option. The function you want here is now called org-html-publish-to-html. There are other similar functions in the other export backends -- e.g., the function to publish to PDF is org-latex-publish-to-pdf. Thus, if you need to find an appropriate publishing function, start by looking for a function named like: org-BACKEND-publish-to-FORMAT. I don't remember how I figured this out, but hopefully it is documented in the manual... (I am not sure about the :recursive or :auto-preamble options, which don't appear in the variable documentation for org-publish-project-alist; if changing :publishing-function on its own does not get this setup working, try removing those options.) > :headline-levels 7 > :auto-preamble t > ) > ("org-static" > :base-directory "~/org/" > :base-extension "css\\|js\\|png\\|jpg\\|gif\\|pdf\\|mp3\\|ogg\\|swf" > :publishing-directory "~/public_html/" > :recursive t > :publishing-function org-publish-attachment > ) > ("org" :components ("org-notes" "org-static")) > )) Again, I think this should work as-is, with the possible exception of the :recursive option. org-publish-attachment is still around. Hope that helps! Best, Richard