emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Neil Smithline <emacs-orgmode@neilsmithline.com>
To: Bastien <bzg@gnu.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Google Summer of Code -- 3 Org projects for our first participation!
Date: Fri, 04 May 2012 18:37:45 -0400	[thread overview]
Message-ID: <4FA45A39.2080108@neilsmithline.com> (raw)
In-Reply-To: <87mx5zrklf.fsf@altern.org>

Bastien,

I've been looking at the bugpile Worg page (very nice page - good work 
Thorsten or whomever) and don't see why you say:

 > I don't see how github could use such
 > a setup to produce HTML files from Org (unless github runs an Emacs
 > batch query for exporting HTML... which seems very unlikely - and
 > wrong by design anyway.

I understand that Emacs is a bit of a behemoth in terms of CPU when 
being started and always in terms of memory. That being said, why does 
it seem "wrong by design" to have Github running an Emacs server and 
sending Org --> HTML jobs to it with emacsclient?

Just a head's up, once you answer the above question, I'm going to ask 
you what can be done to fix the problem :-)

Neil



Neil Smithline
http://www.neilsmithline.com
Proud GNU Emacs user since 1986, v. 18.24.

On 4/26 03:57 , Bastien wrote:
> Hi Neil,
>
> Neil Smithline <emacs-orgmode@neilsmithline.com> writes:
>
>> I've run into this problem dealing with the weak presentation of Org Mode
>> files on Github. Github uses the Ruby gem org-ruby
>> (https://github.com/bdewey/org-ruby) to convert .org files to HTML. I've
>> added a feature or two to org-ruby but really feel that trying to
>> completely re-implement Org Mode in a Ruby gem is a losing battle.
>
> What will help org-ruby (and github's support of org files) is to
> stabilize the syntax of .org files as much as possible.  We are
> currently working in this direction.
>
> org-ruby's main job is to convert .org files into HTML or textile files.
>
>> If I understand the project correctly, a working iOrg could be used to
>> support Github's rendering of .org files. Github could just drop the use of
>> org-ruby and use iOrg as an external converter for formatting .org files.
>
> As I understand it, iOrg will convert .org files to HTML using the
> internal Org's HTML exporter.  I don't see how github could use such
> a setup to produce HTML files from Org (unless github runs an Emacs
> batch query for exporting HTML... which seems very unlikely - and
> wrong by design anyway.
>
> Let's see how iOrg evolves but let's stick to the bugpile for now.
>
> If the list can specifically help about org-ruby issues, let's help!
>
> All best,
>
>> PS: And the answer is "Yes. I am aware that vehemently suggesting a project
>> is equivalent to offering to help with it." :-D
>
> Good :)
>

  parent reply	other threads:[~2012-05-04 22:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-24  5:55 Google Summer of Code -- 3 Org projects for our first participation! Bastien
2012-04-24  7:17 ` Carsten Dominik
2012-04-24  7:18 ` Ian Barton
2012-04-24  8:12   ` Thorsten
2012-04-26  1:42     ` Neil Smithline
2012-04-26  7:48       ` Thorsten Jolitz
2012-04-28 23:12         ` Neil Smithline
2012-04-26  7:57       ` Bastien
2012-04-28 23:30         ` Neil Smithline
2012-04-29  8:26           ` Bastien
2012-04-29  0:20         ` Neil Smithline
2012-04-29  8:22           ` Bastien
2012-05-05  0:19             ` Neil Smithline
2012-05-05  5:39               ` Bastien
2012-05-05 10:52                 ` Bernt Hansen
2012-05-05  9:36               ` Nicolas Goaziou
2012-05-04 22:37         ` Neil Smithline [this message]
2012-05-04 21:04           ` Eric Schulte
2012-04-24  9:54 ` Rasmus
2012-04-24 19:00   ` Achim Gratz
2012-04-24 23:16     ` Rasmus
2012-04-26  8:19       ` Bastien
2012-04-24 11:29 ` Richard Riley
2012-04-24 14:19   ` Andrew Young
2012-05-08  3:42 ` Neil Smithline
2012-05-08  8:06   ` Thorsten Jolitz

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=4FA45A39.2080108@neilsmithline.com \
    --to=emacs-orgmode@neilsmithline.com \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@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/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).