emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Juan Reyero <joanmg@gmail.com>
To: Rick Moynihan <rick.moynihan@gmail.com>
Cc: org-mode Mailing List <emacs-orgmode@gnu.org>
Subject: Re: Announcing org-jekyll
Date: Tue, 2 Feb 2010 14:56:42 +0100	[thread overview]
Message-ID: <55bd243d1002020556s51641fa8q48d3daa9641956b7@mail.gmail.com> (raw)
In-Reply-To: <e85471e31002020237q4adb7ccj3cdc96daa1a029ef@mail.gmail.com>

On Tue, Feb 2, 2010 at 11:37 AM, Rick Moynihan <rick.moynihan@gmail.com> wrote:
> 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
>>> 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.

Souds like the most sensible default, just changed in the repository.
It should only fail if you happened to have a :lang: property in your
entries, though.

> The second problem was that my tags and property keys are all in
> uppercase, yet org-jekyll only works for lower-case keys.

Changed that too.  Now it accepts both lower- and upper-case :BLOG: and :ON:.

> 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....

Changed to create the directories if they don't exist.  Now the
biggest thing still on my list is taking care of accented characters
in entry names.  Looks like some browsers don't like them in urls.

Best,

Juan
-- 
http://juanreyero.com/
http://unarueda.com

      reply	other threads:[~2010-02-02 13:56 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
2010-02-02 13:56       ` Juan Reyero [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=55bd243d1002020556s51641fa8q48d3daa9641956b7@mail.gmail.com \
    --to=joanmg@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rick.moynihan@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).