From: "Clément Lassieur" <clement@lassieur.org>
To: "Thompson, David" <dthompson2@worcester.edu>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Preferred blog format - Markdown or SXML?
Date: Wed, 25 Apr 2018 16:20:22 +0200 [thread overview]
Message-ID: <87sh7jxt95.fsf@lassieur.org> (raw)
In-Reply-To: <CAJ=RwfbBwhN_XBFzvXwUKB8P7VxyPdgd3K+rFhLtdRZcH4ALCQ@mail.gmail.com>
Thompson, David <dthompson2@worcester.edu> writes:
> On Sun, Apr 22, 2018 at 10:22 AM, Adam Massmann <massmannak@gmail.com> wrote:
>>
>> Hi,
>>
>> Pierre Neidhardt <ambrevar@gmail.com> writes:
>>
>>> What about Org-mode?
>>> Rationale:
>>>
>>> http://karl-voit.at/2017/09/23/orgmode-as-markup-only
>>
>> The website uses the haunt [1] static site generator which
>> does not currently support direct reading of org files. However, you
>> could easily export an org file to one of the supported formats (like
>> html).
>
> If anyone writes an org-mode parser in Guile, let me know and I'll add
> support for it in Haunt. I wouldn't even know where to begin with
> trying to parse org files. :)
As a workaround or as a starting point, there is OrgRuby
(https://github.com/wallyqs/org-ruby, packaged for Guix as
ruby-org-ruby). I don't know if Haunt supports Ruby though.
next prev parent reply other threads:[~2018-04-25 14:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-22 8:27 Preferred blog format - Markdown or SXML? Chris Marusich
2018-04-22 8:38 ` Pierre Neidhardt
2018-04-22 14:22 ` Adam Massmann
2018-04-25 14:00 ` Thompson, David
2018-04-25 14:20 ` Clément Lassieur [this message]
2018-04-25 14:39 ` Nicolas Goaziou
2018-04-26 12:50 ` Org-mode for Haunt Ludovic Courtès
2018-04-26 13:58 ` Jose Garza
2018-04-26 17:59 ` swedebugia
2018-04-27 8:07 ` Catonano
2018-04-29 17:09 ` Ludovic Courtès
2018-04-25 13:32 ` Preferred blog format - Markdown or SXML? Adonay Felipe Nogueira
2018-04-22 14:38 ` Ricardo Wurmus
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sh7jxt95.fsf@lassieur.org \
--to=clement@lassieur.org \
--cc=dthompson2@worcester.edu \
--cc=guix-devel@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/guix.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).