From: Rick Moynihan <rick.moynihan@gmail.com>
To: Juan Reyero <joanmg@gmail.com>
Cc: org-mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Announcing org-jekyll
Date: Tue, 2 Feb 2010 10:37:30 +0000 [thread overview]
Message-ID: <e85471e31002020237q4adb7ccj3cdc96daa1a029ef@mail.gmail.com> (raw)
In-Reply-To: <55bd243d1002011114y1c1058an1f427aaf23efb83b@mail.gmail.com>
Replies inline below:
On 1 February 2010 19:14, Juan Reyero <joanmg@gmail.com> wrote:
> On Mon, Feb 1, 2010 at 12:23 PM, Rick Moynihan <rick.moynihan@gmail.com> wrote:
>> On 29 January 2010 23:16, Juan Reyero <joanmg@gmail.com> wrote:
>>> Full description: http://juanreyero.com/open/org-jekyll/
>>> Source code: http://github.com/juanre/org-jekyll
>>
>> I'm not entirely clear on how the org-publish-project-alist relates to
>> org-jekyll and org-jekyll-export-blog? What do you need to do to set
>> this up, other than annotate headlines with :blog: keywords and :on:
>> properties?
>
> You set it up so that the files that contain blog entries belong to an
> org-publish project, as described for example in
> http://orgmode.org/worg/org-tutorials/org-publish-html-tutorial.php
>
> The idea is that you might want to combine a blog with a bunch of
> org-published files, as I do in http://juanreyero.com and
> http://greaterskies.com, and you shouldn't have to spend too much time
> separating the two things. So it boils down to defining your
> org-publish-project-alist. Then you open a file that belongs to the
> project and do org-jekyll-export-blog or
> org-jekyll-export-current-entry, depending on what you need.
Yes, I like this flexibility.
>> I've found that calling org-jekyll-export-blog, seems to do nothing...
>
> It should, if the file from which you are calling is part of an
> org-publish project, and there are entries with the :blog: tag and the
> :on: property.
Ok, it turns out that there were several problems I had... After some
time in the emacs debugger, it turned out that the default values for
org-jekyll-category and org-jekyll-localize-dir are non-nil... which
was causing the _posts/ directory to be set to a directory that
doesn't exist. Overriding these to nil fixed the first problem.
The second problem was that my tags and property keys are all in
uppercase, yet org-jekyll only works for lower-case keys.
I seem to be up and running with it for now... I just need to modify
my setup a bit more to account for the changes... But this definitely
seems a lot less hacky than the happyblogger setup I was playing
with!!
I think setting both of those vars to default to nil would make
sense... As I'd imagine people would probably want to start with a
minimal config/setup and grow into the more advanced multi-lingual
features you have.
Also it would be nice for org-jekyll-export-blog to fail with an
error, rather than just dying silently. Alternatively even better
might be for it to construct the _post and category directories it
needs if they don't already exist....
Great work though!!!! I've been waiting for something like this for
years!!! (Though I'm also a tiny bit dissapointed that you stole my
march; as I was looking forward to learning a bit more Emacs Lisp and
reworking happyblogger into something like this).... But again,
thanks a bunch this is a valuable addition to the org community!
--
Rick Moynihan
http://twitter.com/RickMoynihan
http://delicious.com/InkyHarmonics
http://sourcesmouth.co.uk/
next prev parent reply other threads:[~2010-02-02 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-29 23:16 Announcing org-jekyll Juan Reyero
2010-02-01 8:38 ` Carsten Dominik
2010-02-01 9:42 ` Carsten Dominik
2010-02-01 20:20 ` Eric Schulte
2010-02-02 12:57 ` Juan Reyero
2010-02-03 15:17 ` Carsten Dominik
2010-02-01 11:23 ` Rick Moynihan
2010-02-01 19:14 ` Juan Reyero
2010-02-02 10:37 ` Rick Moynihan [this message]
2010-02-02 13:56 ` Juan Reyero
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=e85471e31002020237q4adb7ccj3cdc96daa1a029ef@mail.gmail.com \
--to=rick.moynihan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=joanmg@gmail.com \
/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).