From: David O'Toole <dto@gnu.org>
To: Austin Frank <austin.frank@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-blog report
Date: Thu, 31 May 2007 08:48:38 -0400 [thread overview]
Message-ID: <m36469rwex.fsf@gnu.org> (raw)
In-Reply-To: <m0ejky1633.fsf@gmail.com> (Austin Frank's message of "Wed\, 30 May 2007 15\:09\:36 -0400")
> First, is this a documentation bug?
>
> ;; '("blog" . (:base-directory "~/blog/"
Yes. thanks for identifying it.
> org-blog-new-post and org-blog-finish-post work as expected, but
> org-publish does not. When I interactively org-publish the blog project
> I get the attached index.org in the base-directory, the attached
> blog.xml in the publishing-directory, and no html files anywhere. Doing
> an interactive org-export-as-html on the attached finished blog entry
> does correctly produce an html file even though publishing the project
> does not.
I'm not sure how to test this. It works fine for me. I am using the
latest versions of both org-publish.el and org-blog.el and these are
on the website in the directory http://dto.freeshell.org/e/
Maybe you can load those into emacs and see if the problem improves?
If not, can you try running it under edebug?
> - what's the difference between blog-title and index-title in the
> plist?
blog-title is the title of the exported RSS feed. index-title is the title of
the exported index.html page.
This is not documented, sorry.
> - in files generated by org-blog-new-post, where will the #+TITLE and
> #+DESCRIPTION show up on the page?
This is also not documented. I'm probably going to remove the
#+DESCRIPTION functionality.
> - is content before the first heading published?
Do you mean in a blog post?
--
David O'Toole
dto@gnu.org
http://dto.freeshell.org/notebook/
parent reply other threads:[~2007-05-31 12:48 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <m0ejky1633.fsf@gmail.com>]
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=m36469rwex.fsf@gnu.org \
--to=dto@gnu.org \
--cc=austin.frank@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).