From: Sebastian Rose <sebastian_rose@gmx.de>
To: emacs-orgmode@gnu.org
Cc: Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: publish templates - include stylesheet
Date: Sat, 27 Sep 2008 23:45:56 +0200 [thread overview]
Message-ID: <48DEA994.5080702@gmx.de> (raw)
In-Reply-To: <87bpyaw421.fsf@paldesk2.palstudio>
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!
>
>
prev parent reply other threads:[~2008-09-27 21:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-27 5:28 publish templates - include stylesheet plutek-infinity
2008-09-27 21:45 ` Sebastian Rose [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48DEA994.5080702@gmx.de \
--to=sebastian_rose@gmx.de \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).