From: Juan Reyero <joanmg@gmail.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: org-mode Mailing List <emacs-orgmode@gnu.org>,
Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Need help exporting subtrees to html
Date: Fri, 1 Jan 2010 14:33:48 +0100 [thread overview]
Message-ID: <55bd243d1001010533s13691049pbc31c2be6d8bcb91@mail.gmail.com> (raw)
In-Reply-To: <87ljgigbw6.fsf@gmail.com>
On Thu, Dec 31, 2009 at 8:51 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
> Juan Reyero <joanmg@gmail.com> writes:
>
>> On Thu, Dec 31, 2009 at 6:15 PM, Eric Schulte <schulte.eric@gmail.com> wrote:
>>> Juan Reyero <joanmg@gmail.com> writes:
>>>
>>>> On Thu, Dec 31, 2009 at 9:15 AM, Carsten Dominik
>>>> <carsten.dominik@gmail.com> wrote:
>>>>> On Dec 27, 2009, at 8:31 PM, Juan Reyero wrote:
>>>>>> On Sun, Dec 27, 2009 at 7:35 PM, Carsten Dominik
>>>>>> <carsten.dominik@gmail.com> wrote:
>>>>>>> On Dec 27, 2009, at 5:34 PM, Juan Reyero wrote:
>>>>>>>> I have written a function to export org-mode subtrees as jekyll posts,
>>>>>>>> http://juanreyero.com/open/org-jekyll/ The idea is that any entry in
>>>>>>>> an org-publish project that has a :blog: keyword and an :on: property
>>>>>>>> with a timestamp should be exported to a _posts directory with the
>>>>>>>> year-month-day-title.html that jekyll expects, with the properties as
>>>>>>>> front-matter.
>>> If it helps, I've been doing something similar to support publishing
>>> updates on the org-babel development -- using the code shown here [1]
>>> under the "Development Updates" section. This generates a files in
>>> _posts for each subtree of of the "tasks" and "bugs" sections which have
>>> a time-stamp in their properties. It should be fairly straightforward
>>> to adapt this code to export all properties as YAML frontmatter.
>>
>> It is exactly what I did :-). I found your code here [1], and adapted
>> it so that it would use files in an org-publish project and would
>> export properties.
>
> Ah, I should have read the thread more carefully :)
>
>> So thank you very much for making it available. It does, however,
>> have the same problem I find: the header level with which the piece is
>> exported (h1, h2, etc) depends on the outline level on which the item
>> you export happened to be. I was hoping to export the chunks
>> independently of where they were written.
>>
>
> So this turned out to be somewhat tricky. I was able to adjust my
> previous code so that every subtree will be promoted to a top-level
> heading before export by adding the following (this change can also be
> seen in my published code here [1]).
>
> --8<---------------cut here---------------start------------->8---
> (org-narrow-to-subtree)
> (let ((level (- (org-outline-level) 1))
> (contents (buffer-substring (point-min) (point-max))))
> (dotimes (n level nil) (org-promote-subtree))
> (setq html (org-export-as-html nil nil nil 'string t nil))
> (set-buffer org-buffer)
> (delete-region (point-min) (point-max))
> (insert contents)
> (save-buffer))
> (widen)
> --8<---------------cut here---------------end--------------->8---
It works! Thank you _very_ much. I've just had to add a
org-reduced-level to the org-outline-level, like
(org-reduced-level (org-outline-level)).
I've updated it in github and on
http://juanreyero.com/open/org-jekyll/, and I'll try to add something
to worg this afternoon.
Best,
Juan
> Footnotes:
> [1] http://eschulte.github.com/babel-dev/publish.html
--
http://juanreyero.com/
http://unarueda.com
prev parent reply other threads:[~2010-01-01 13:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-27 16:34 Need help exporting subtrees to html Juan Reyero
2009-12-27 18:35 ` Carsten Dominik
2009-12-27 19:31 ` Juan Reyero
2009-12-31 8:15 ` Carsten Dominik
2009-12-31 13:50 ` Juan Reyero
2009-12-31 17:15 ` Eric Schulte
2009-12-31 17:17 ` Eric Schulte
2009-12-31 18:02 ` Juan Reyero
2009-12-31 19:51 ` Eric Schulte
2010-01-01 13:33 ` 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=55bd243d1001010533s13691049pbc31c2be6d8bcb91@mail.gmail.com \
--to=joanmg@gmail.com \
--cc=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).