From mboxrd@z Thu Jan 1 00:00:00 1970 From: Lawrence Bottorff Subject: Publishing versus normal exporting Date: Fri, 17 Feb 2017 10:59:43 -0500 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c04f74e86eea70548bc0013 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:45762) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cekwj-0001ra-PB for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 10:59:46 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cekwi-0007na-My for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 10:59:45 -0500 Received: from mail-ot0-x235.google.com ([2607:f8b0:4003:c0f::235]:33054) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1cekwi-0007nI-HW for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 10:59:44 -0500 Received: by mail-ot0-x235.google.com with SMTP id k4so13791594otc.0 for ; Fri, 17 Feb 2017 07:59:44 -0800 (PST) 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" To: emacs-orgmode Mailinglist --94eb2c04f74e86eea70548bc0013 Content-Type: text/plain; charset=UTF-8 I'm looking at this which seems to suggest a difference between "publishing" and normal export (e.g., C-c C-e h o to get an HTML export). The Emacs configuration given here would or would not be in force with a normal export? What this "complex publishing configuration" gives is exactly what I want, but only for one project. Is there a way to keep normal export -- and possibly multiple projects -- separate? LB --94eb2c04f74e86eea70548bc0013 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
I'm looking at=C2=A0this=C2=A0which seems to suggest a diffe= rence between "publishing" and normal export (e.g., C-c C-e h o t= o get an HTML export). The Emacs configuration given=C2=A0here=C2=A0wou= ld or would not be in force with a normal export? What this "complex p= ublishing configuration" gives is exactly what I want, but only for on= e project. Is there a way to keep normal export -- and possibly multiple pr= ojects -- separate?

LB

--94eb2c04f74e86eea70548bc0013-- From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: Publishing versus normal exporting Date: Fri, 17 Feb 2017 11:43:13 -0500 Message-ID: <87ino8zs2m.fsf@alphaville.usersys.redhat.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:58269) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1celd3-0001Ju-ST for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 11:43:30 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1celd0-00089f-Qv for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 11:43:29 -0500 Received: from [195.159.176.226] (port=52433 helo=blaine.gmane.org) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1celd0-000893-K7 for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 11:43:26 -0500 Received: from list by blaine.gmane.org with local (Exim 4.84_2) (envelope-from ) id 1celcq-0000HD-CX for emacs-orgmode@gnu.org; Fri, 17 Feb 2017 17:43:16 +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" To: emacs-orgmode@gnu.org Lawrence Bottorff writes: > I'm looking at this which seems to suggest a difference between > "publishing" and normal export (e.g., C-c C-e h o to get an HTML > export). The Emacs configuration given here would or would not be in > force with a normal export? What this "complex publishing > configuration" gives is exactly what I want, but only for one > project. Is there a way to keep normal export -- and possibly > multiple projects -- separate? > It would not be in force for normal export. The config file comes into force when you invoke org-publish and specify a project. You can specify different configs for different projects by adding entries to org-publish-project-alist. In fact, the complex config specifies four projects, although it is true that three of them are components of the fourth. Generally, you'd publish the "website" project and the sub-projects would be published, but you can publish them individually as well. -- Nick