From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sebastian Rose Subject: Re: publish templates - include stylesheet Date: Sat, 27 Sep 2008 23:45:56 +0200 Message-ID: <48DEA994.5080702@gmx.de> References: <87bpyaw421.fsf@paldesk2.palstudio> Reply-To: sebastian_rose@gmx.de Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1KjhbW-0001dn-GX for emacs-orgmode@gnu.org; Sat, 27 Sep 2008 17:45:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1KjhbU-0001dY-L3 for emacs-orgmode@gnu.org; Sat, 27 Sep 2008 17:45:29 -0400 Received: from [199.232.76.173] (port=44176 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1KjhbU-0001dV-F7 for emacs-orgmode@gnu.org; Sat, 27 Sep 2008 17:45:28 -0400 Received: from mail.gmx.net ([213.165.64.20]:57448) by monty-python.gnu.org with smtp (Exim 4.60) (envelope-from ) id 1KjhbT-00086U-TW for emacs-orgmode@gnu.org; Sat, 27 Sep 2008 17:45:28 -0400 In-Reply-To: <87bpyaw421.fsf@paldesk2.palstudio> 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 Cc: Carsten Dominik Hi plutek-infinity, right, it does not work here either. Funny enough, it works or files in my projects base directory. Hmmm -strange. I have to admit that I'm not realy shure how I tested this for files in subdirectories when I wrote the tutorial. This is what the manual says about the #+SETUPFILE: `#+SETUPFILE: file' This line defines a file that holds more in-buffer setup. Normally this is entirely ignored. Only when the buffer is parsed for option-setting lines (i.e. when starting Org mode for a file, when pressing `C-c C-c' in a settings line, or when exporting), then the contents of this file are parsed as if they had been included in the buffer. In particlar, the file can be any other Org mode file with internal setup. You can visit the file the cursor is in the line with `C-c ''. (...should note the last sentence in the tutorial...) And yes, the export-options-template lines are read for all files regardless of level. But the '* COMMENT html style specifications' part is only read for files directly in the projects base-directory. Carsten: this is the link to the section in the tutorial: http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php#sec-5.3 What to do here? Should I change the tutorial in this part? It works so wonderfull for all the files in base-directory. Only one file to change to change the settings for many many files. And it seems that the current behaviour is not intended, is it? The ':style' options in org-publish-projects-alist das not work for sub directories either, so the combination of the special comment section is and #+SETUPFILE: is the only way to set the style in a central place. ??? - Sebastian plutek-infinity wrote: > greetings! > > i'm following the org-publish tutorial on worg, and have hit a snag: > > the html style specifications "special comment section" successfully includes an external stylesheet when i put it in an org file prior to publishing, but when i move it to the level-N.org files as outlined in the tutorial, the stylesheet no longer gets referenced in the published html file. i know the level-N.org file is being used, since the export options lines which it contains ARE being read. it seems that just the html style block is being ignored. > > as far as i can see, i've set things up as they should be -- any hints as to what i might look into to debug this? > > thanks in advance.... cheers! > >