From mboxrd@z Thu Jan 1 00:00:00 1970 From: mdl@imapmail.org Subject: Org publish hierarchies and style variable Date: Wed, 29 Oct 2008 10:37:01 -0500 Message-ID: <87d4hj9zvm.fsf@fastmail.fm> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KvD6R-0000vv-9r for emacs-orgmode@gnu.org; Wed, 29 Oct 2008 11:36:59 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KvD6N-0000tU-Jy for emacs-orgmode@gnu.org; Wed, 29 Oct 2008 11:36:58 -0400 Received: from [199.232.76.173] (port=47943 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KvD6N-0000tN-2m for emacs-orgmode@gnu.org; Wed, 29 Oct 2008 11:36:55 -0400 Received: from out1.smtp.messagingengine.com ([66.111.4.25]:53533) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1KvD6M-0000xe-J5 for emacs-orgmode@gnu.org; Wed, 29 Oct 2008 11:36:55 -0400 Received: from matt-desktop (vu019215.valpo.edu [152.228.168.123]) by mail.messagingengine.com (Postfix) with ESMTPA id 7C96945632 for ; Wed, 29 Oct 2008 11:36:50 -0400 (EDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org A question: The org-publish tutorial recommends the use of template files for setting the relative link to the stylesheet for nested directories to be published to html. - http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php E.g., For first level directories such as ~/org/ |- css/ | |- stylesheet.css |- index.org |- Emacs | |- index.org ~/org/Emacs/index.org would contain the following: #+SETUPFILE: ~/.emacs.d/level-1.org which points to a setupfile with the option: #+STYLE: My question: Instead of this method, which I find a little tedious, I've created a hardlink to the master css directory in each subdirectory of my project. As a result the, css files get copied to each subdirectory in my public web directory and I only need to specify a single style option in my org-publish-alist. Apart from taking up extra disk space on the server (and thus being less economical), are there any other potential problems with this approach? I'm using org as a wiki and have a lot of org files in each subdirectory. This approach seems easier than having to add and tweak the SETUPFILE option for each new org file. --- Matt Lundin mdl at imapmail dot org