From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Eric Schulte" Subject: Re: Announcing org-jekyll Date: Mon, 01 Feb 2010 13:20:04 -0700 Message-ID: <87aavsn1xn.fsf@gmail.com> References: <55bd243d1001291516m2b3fe054u8da0f64edf6b8d25@mail.gmail.com> <243263DF-04B0-4889-A72D-CBEB7E3C87DD@uva.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Nc2km-0006OJ-IU for emacs-orgmode@gnu.org; Mon, 01 Feb 2010 15:20:12 -0500 Received: from [199.232.76.173] (port=59641 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Nc2km-0006O3-4t for emacs-orgmode@gnu.org; Mon, 01 Feb 2010 15:20:12 -0500 Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60) (envelope-from ) id 1Nc2kj-0004dY-Ir for emacs-orgmode@gnu.org; Mon, 01 Feb 2010 15:20:11 -0500 Received: from mail-pz0-f185.google.com ([209.85.222.185]:50708) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Nc2ki-0004dH-Vn for emacs-orgmode@gnu.org; Mon, 01 Feb 2010 15:20:09 -0500 Received: by pzk15 with SMTP id 15so4537987pzk.25 for ; Mon, 01 Feb 2010 12:20:07 -0800 (PST) In-Reply-To: <243263DF-04B0-4889-A72D-CBEB7E3C87DD@uva.nl> (Carsten Dominik's message of "Mon, 1 Feb 2010 10:42:06 +0100") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Carsten Dominik Cc: org-mode Mailing List , Carsten Dominik So to jump onto this thread that Carsten unwittingly brought back to life ;) I have been exporting org-mode subtrees to jekyll blog posts on a couple of projects, and I've found it really handy - resulting in more attractive web pages than I'm able to generate directly from org - for the liquid syntax which jekyll provides for programmatic generation of elements of html files - and for the ability to automatically generate xml/atom/rss from my projects One issue that I've not been able to solve is the resolution of intra-file links when I'm exporting subtrees to external files. For example say I have the following file ,----[example.org] | * top | ** subtopic | :PROPERTIES: | :CUSTOM_ID: subtopic | :END: | stuff | | ** another topic | see stuff in [[subtopic]] `---- after I've exported the subtrees to separate files for processing by jekyll, all of my intra-file links are broken. I wonder if a generalization of this issue might have wide enough appeal to merit an org-mode based solution. Specifically would it be possible to add support for exporting subtrees to external files, and updating all links within the subtree based on the new location of the exported file (i.e. adjusting all intra-file links to point to the original file)? Taking the above idea one step further, if say each subtree has an "EXPORT_FILE_NAME" property then it would be great to support link maintenance during export of all such subtrees in a file, so for example the following file ,----[example.org] | * top | | ** section one | :PROPERTIES: | :EXPORT_FILE_NAME: section-one | :END: | | *** subtopic | :PROPERTIES: | :CUSTOM_ID: subtopic | :END: | stuff | | ** another topic | :PROPERTIES: | :EXPORT_FILE_NAME: another-topic | :END: | see stuff in [[subtopic]] `---- could export to ,----[section-one.org] | * section one | :PROPERTIES: | :EXPORT_FILE_NAME: section-one | :END: | | ** subtopic | :PROPERTIES: | :CUSTOM_ID: subtopic | :END: | stuff `---- and ,----[another-topic.org] | * another topic | :PROPERTIES: | :EXPORT_FILE_NAME: another-topic | :END: | see stuff in [[file:section-one.org::subtopic][subtopic]] `---- I hope the above example is clear. While writing this up I noticed the existence of an "EXPORT_FILE_NAME" property however I was unable to use it to successfully export a subtree. It may be that the behavior I've described is only useful in the case of jekyll export, in which case I may try my hand at hacking a solution together. Either way I'd be interested to hear peoples thoughts or if I'm missing some existing functionality. Thanks -- Eric Carsten Dominik writes: > Sorry, this reply was in the wrong thread and is therefore meaningless. > > - Carsten > > On Feb 1, 2010, at 9:38 AM, Carsten Dominik wrote: > >> Hi Juan, >> >> I like this idea, and I have implemented it. Please use the >> property HTML_CONTAINER_CLASS. And let me know if it works! >> >> HTH >> >> - Carsten >> >> On Jan 30, 2010, at 12:16 AM, Juan Reyero wrote: >> >>> Greetings, >>> >>> I've been toying around with a small package to export entries as a >>> Jekyll blog. It is different from other approaches I am aware of in >>> that it will find your blog entries anywhere in the files belonging >>> to >>> a project, and it will pass properties along to Jekyll as yaml front >>> matter. It also includes some support for localization. >>> >>> Full description: http://juanreyero.com/open/org-jekyll/ >>> Source code: http://github.com/juanre/org-jekyll >>> >>> Best regards, >>> >>> Juan > > - Carsten > > > > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacs-orgmode@gnu.org > http://lists.gnu.org/mailman/listinfo/emacs-orgmode