From: Richard Riley <rileyrgdev@googlemail.com>
To: Matthew Lundin <mdl@imapmail.org>
Cc: org-mode <emacs-orgmode@gnu.org>,
Richard Riley <rileyrgdev@googlemail.com>
Subject: Re: org-publish-file
Date: Thu, 04 Dec 2008 19:06:27 +0100 [thread overview]
Message-ID: <49381c54.170d660a.6b58.0b44@mx.google.com> (raw)
In-Reply-To: <87d4g7zw7j.fsf@fastmail.fm> (Matthew Lundin's message of "Thu, 04 Dec 2008 11:28:16 -0600")
Matthew Lundin <mdl@imapmail.org> writes:
> Hi Richard,
>
> Richard Riley <rileyrgdev@googlemail.com> writes:
>
>> If I edit a file in an org web subdirectory and then publish that file it does
>> not get published with the style sheet link content.
>>
>> e.g I have a file index.org in rgr-source/bike and when I publish it the
>> destination rgr-source/bike/index.html does not include the :style as
>> specified in web-org below.
>>
> I assume you mean that the exported html does not contain the
> stylesheet line at all. I can't seem to replicate this behavior. When
> I publish org files recursively, the link to the stylesheet appears in
> all exported html files, regardless of their directory level.
I am referring to publishing the single file using org-publish-file
Possibly its as designed, but I'm not sure that would be the right thing.
>
> [snip]
>> ("web-org"
>> :base-directory ,rgr-source
>> :publishing-directory ,rgr-publish
>> :recursive t
>> :base-extension "org"
>> :publishing-function org-publish-org-to-html
>> :section-numbers nil
>> :style "<link rel=stylesheet
>> href=\"./style.css\"
>> type=\"text/css\">"
>> :auto-preamble t
>> :auto-postamble t
>> :preamble ,(format "<div id='Content'><a href='../'>Back</a> - <a href='%s'>Home</a>" rgr-home)
>> :postamble "</div>"
>> :author nil
>> )
> [snip]
>
> Is the css file also exported to the subdirectory "/rgr-source/bike"?
> If not, the relative link won't find the file. I believe you'll either
> need to use an absolute link or specify a different relative link
> (e.g., "../style.css") using the #+STYLE option in
> "/rgr-source/bike/index.org".
Each dir has a style.css which includes ../style.css. That is not the
issue. Recursive publish works fine.
>
> Regards,
>
> Matt
--
important and urgent problems of the technology of today are no longer the satisfactions of the primary needs or of archetypal wishes, but the reparation of the evils and damages by the technology of yesterday. ~Dennis Gabor, Innovations: Scientific, Technological and Social, 1970
prev parent reply other threads:[~2008-12-04 18:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 16:31 org-publish-file Richard Riley
2008-12-04 17:28 ` org-publish-file Matthew Lundin
2008-12-04 18:06 ` Richard Riley [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=49381c54.170d660a.6b58.0b44@mx.google.com \
--to=rileyrgdev@googlemail.com \
--cc=emacs-orgmode@gnu.org \
--cc=mdl@imapmail.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).