emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tom Alexander <tomalexander@paphus.com>
To: emacs-orgmode@gnu.org
Subject: Re: Introducing Octopress Exporter
Date: Thu, 2 Aug 2012 13:44:20 +0000 (UTC)	[thread overview]
Message-ID: <loom.20120802T153525-416@post.gmane.org> (raw)
In-Reply-To: CA+5B0FMC+SPH9F--vepZRQ0rfneBHbnuG5Y7n+FmMSEptMH4nw@mail.gmail.com

Aurélien Aptel <aurelien.aptel <at> gmail.com> writes:

> I've never heard of octopress, interesting. The only thing I don't
> like is how comments are handled. Since it's all static you relying on
> an external service like Disqus. I'm not so fond of losing control
> over user contribution like that. Besides, the actual service (disqus)
> is pretty terrible anyway. I'm always pissed when the comment I sent
> gets processed in weird ways yet doesn't do verbatim/code blocks.
> On Thu, Aug 2, 2012 at 1:21 AM, Tom Alexander <tomalexander <at> paphus.com> 
> > The important changes are all at the bottom of the file. Basically I
> > just grab the text before the html preprocessor gets to it and go
> > through line-by-line to find the code blocks.
> Have you tried Nicolas Goaziou new parser? org-element.el is a big
> improvement for org-mode IMHO.

Yeah, the whole Disqus comments thing can be a pain, but since the pages are all 
static its a lot easier on your web server and possibly faster since you don't 
have a server side language rendering the page. Also, having the posts written 
mostly in plain HTML (with some special markup for the header and code blocks) 
its easy for anyone who has written HTML to pick it up, and even easier to use 
other tools like org-mode to post to it.

In terms of org-element, I did look at it when I was writing this, and it looks 
significantly better, but I was getting errors loading org-mode from the 
repository at the time. After writing this I learned that apparently master is 
the development branch for this project, not the stable branch. I might re-write 
this for the new exporter later since I'm sure the old exporter is on its way 

  reply	other threads:[~2012-08-02 13:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-01 23:21 Introducing Octopress Exporter Tom Alexander
2012-08-02  9:45 ` Aurélien Aptel
2012-08-02 13:44   ` Tom Alexander [this message]
2012-08-02 14:37   ` Jambunathan K
2012-08-06 22:28   ` Neil Smithline
2012-08-07  2:48     ` Neil Smithline
2012-08-07  9:52       ` The Quantified Shower (was: Introducing Octopress Exporter) Bastien
2012-08-07 12:32         ` The Quantified Shower Christopher J. White
2012-08-09 10:17           ` Aurélien Aptel
2012-08-07 13:07         ` The Quantified Shower (was: Introducing Octopress Exporter) Nick Dokos
2012-08-07 13:13           ` Nick Dokos
2012-08-07 17:27             ` The Quantified Shower Bastien
2012-08-07 20:39               ` brian powell
2012-08-08 12:46             ` Karl Voit
2012-08-08 17:30           ` Jambunathan K
2012-08-10  7:50             ` Bastien
2012-08-13 10:56               ` A tidy file maketh a tidy mind? 'Mash
2012-08-14  7:46                 ` Bastien
2012-08-14 13:10                 ` Eric Schulte
2012-08-14 13:55                   ` 'Mash (Thomas Herbert)
2012-08-14 21:50                   ` Bastien
2012-08-07 13:08         ` The Quantified Shower (was: Introducing Octopress Exporter) Myles English
2012-08-03  7:15 ` Introducing Octopress Exporter Bastien

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:

  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=loom.20120802T153525-416@post.gmane.org \
    --to=tomalexander@paphus.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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