From: "Chris wallace" <crassshed@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: [David O'Toole] Fwd: Re: org-publish future ?
Date: Wed, 7 Jun 2006 15:00:58 +0000 [thread overview]
Message-ID: <9bcdfad70606070800q5eb3a769o29e7ebb49eeb99ad@mail.gmail.com> (raw)
In-Reply-To: <33a44a817ed2058827091b0a638872e2@science.uva.nl>
[-- Attachment #1.1: Type: text/plain, Size: 1538 bytes --]
On 07/06/06, Carsten Dominik <dominik@science.uva.nl> wrote:
>
>
> On Jun 6, 2006, at 18:02, Chris wallace wrote:
>
> >
> > PS. On the subject of org-publish (sort of), one of the things I like
> > most about org-mode is that I can have Readme.org files scattered over
> > a number of directories and have them all included in the agenda.
> > However, org-publish assumes all org files for a single project reside
> > in a single directory. I wonder if I am the only one who has several
> > directories per project?
>
> I think you can already use the :include parameter to do this - at
> least I hope that you can give absolute path names there. If not, i
> would consider this a bug.
So either this is a bug or I'm mis-using the :include parameter. I have
org-publish-project-alist set as follows:
org-publish-project-alist is a variable defined in `org-publish.el'.
Its value is
(("bright" :base-directory "~/bright"
:base-extension "org"
:include ("/home/chris/bright/chr5/cng/Readme.org"
"/home/chris/bright/chr5/phase2/Readme.org")
:publishing-directory "~/public_html/org"
:with-section-numbers nil
:table-of-contents t
:style "<link rel=stylesheet href=\"/~chris/styles/wiki-style.css\"
type=\"text/css\">"))
When I do M-x org-publish bright the *.org files in ~/bright are published,
but the included files are not. I also tried with filenames relative to
~/public/org; same result. How should I be setting :include?
This is with org v. 4.36, org-publish v. 1.70, emacs v. 22.0.50.2
Chris.
- Carsten
>
>
[-- Attachment #1.2: Type: text/html, Size: 2298 bytes --]
[-- Attachment #2: Type: text/plain, Size: 149 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2006-06-07 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-05 21:19 [David O'Toole] Fwd: Re: org-publish future ? David O'Toole
2006-06-06 10:29 ` Carsten Dominik
2006-06-06 10:48 ` David O'Toole
2006-06-06 13:54 ` Michael Olson
2006-06-06 14:17 ` Carsten Dominik
2006-06-06 14:38 ` Michael Olson
[not found] ` <9bcdfad70606060901q52c0097fgde12d5d6ffcf83e9@mail.gmail.com>
2006-06-06 16:02 ` Fwd: " Chris wallace
2006-06-07 13:06 ` Carsten Dominik
2006-06-07 15:00 ` Chris wallace [this message]
2006-06-07 15:25 ` David O'Toole
2006-06-10 12:24 ` Bastien
2006-06-07 17:09 ` Christian Schlauer
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=9bcdfad70606070800q5eb3a769o29e7ebb49eeb99ad@mail.gmail.com \
--to=crassshed@gmail.com \
--cc=dominik@science.uva.nl \
--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).