From: "Chris wallace" <crassshed@gmail.com>
To: David O'Toole <dto@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-publish v1.71
Date: Fri, 9 Jun 2006 09:16:42 +0000 [thread overview]
Message-ID: <9bcdfad70606090216h681184ear2d271d7321817861@mail.gmail.com> (raw)
In-Reply-To: <m3verbfm00.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 1161 bytes --]
On 08/06/06, David O'Toole <dto@gnu.org> wrote:
>
>
> Bugfix release. Should now allow absolute filenames in the :include
> directive.
>
>
Thanks. It works. Just one more request, so I can use this with my files
spread across many directories.
When I have
(setq org-publish-project-alist
(list
'("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"))))
The two Readme.org files both get published as
~/public_html/org/Readme.org. I would really like them to be
~/public_html/org/chr5_cng_Readme.html and
~/public_html/org/chr5_phase2_Readme.org. Ie with the directory relative to
:base-directory included in the file name. Is this possible?
My working situation is that under project bright, important directories
have a Readme.org file containing notes relating to that sub-directory.
It's handy for writing the notes for the filename to always be Readme.org,
but less handy for publishing so that my colleagues can see where I'm up to.
Thanks, Chris.
[-- Attachment #1.2: Type: text/html, Size: 1897 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-09 9:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-08 20:09 org-publish v1.71 David O'Toole
2006-06-09 9:16 ` Chris wallace [this message]
2006-06-10 15:44 ` David O'Toole
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=9bcdfad70606090216h681184ear2d271d7321817861@mail.gmail.com \
--to=crassshed@gmail.com \
--cc=dto@gnu.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 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).