From: mdl@imapmail.org
To: emacs-orgmode@gnu.org
Subject: Org publish hierarchies and style variable
Date: Wed, 29 Oct 2008 10:37:01 -0500 [thread overview]
Message-ID: <87d4hj9zvm.fsf@fastmail.fm> (raw)
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: <link rel="stylesheet" type="text/css"\
href="../stylesheet.css" />
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
next reply other threads:[~2008-10-29 15:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-29 15:37 mdl [this message]
2008-10-29 17:59 ` Org publish hierarchies and style variable Bernt Hansen
2008-10-30 3:00 ` Matthew Lundin
2008-10-30 10:38 ` Richard Riley
2008-10-30 15:19 ` Sebastian Rose
2008-10-30 15:06 ` Richard Riley
2008-10-30 17:32 ` Sebastian Rose
2008-10-30 17:04 ` Richard Riley
2008-10-29 18:40 ` Sebastian Rose
2008-10-29 18:59 ` Sebastian Rose
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d4hj9zvm.fsf@fastmail.fm \
--to=mdl@imapmail.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.