emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rustom Mody <rustompmody@gmail.com>
To: "Aurélien Aptel" <aurelien.aptel@gmail.com>
Cc: ragel-users@complang.org, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: GSoC 2012 -- Elisp backend for Ragel
Date: Fri, 23 Mar 2012 17:06:35 +0530	[thread overview]
Message-ID: <CAJ+Teof96icFpJdEgbMiZssUdgN7MTUUiQM+uW3pnv44SZGoJg@mail.gmail.com> (raw)
In-Reply-To: <CA+5B0FPLmMzJw0TJ1os_gYfZSU17=_ZzC8dkpmNUF=SXW1NK5w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1085 bytes --]

On Fri, Mar 23, 2012 at 4:42 PM, Aurélien Aptel <aurelien.aptel@gmail.com>wrote:

> So, as an experienced org-mode developper you're saying it's very
> hard? I should focus on the ragel part in the application and try to
> go as far as i can for org-mode then. I still need something I can be
> evaluated to for the mid-term and final evaluation.
>
> Can you be my mentor? If no one can I should apply for another project :/
>

I am rather far from being an org mode developer; just a user.

Adding a ragel backend for elisp on its own is too small for a gsoc project
Using ragelized elisp to rewrite orgmode is a wonderful project, but large.

The best solution is to chalk out a subset of the latter and work at that

Ive cced the ragel list in case Adrian Thurston, the ragel author, thinks
differently

For the first Adrian and the ragel list is your best bet.
For the second the orgmode list and developers.

For myself I am interested and would like to be informed. I dont think I
know enough of the internals of either to be the sole responsible party.

[-- Attachment #2: Type: text/html, Size: 1359 bytes --]

  reply	other threads:[~2012-03-23 11:36 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-22 13:43 GSoC 2012 -- Elisp backend for Ragel Rustom Mody
2012-03-23 11:12 ` Aurélien Aptel
2012-03-23 11:36   ` Rustom Mody [this message]
     [not found]     ` <CAJ+TeoebkVTLs9nrDTH_6xvzvkk1vTEZDL2iHmEAkTUfZRjpjQ@mail.gmail.com>
     [not found]       ` <CAJ+TeoebkVTLs9nrDTH_6xvzvkk1vTEZDL2iHmEAkTUfZRjpjQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-03-25  4:17         ` Rustom Mody
2012-03-25  6:55           ` Rustom Mody
2012-03-25 10:06           ` Aurélien Aptel
2012-03-25 11:40             ` Nicolas Goaziou
2012-03-25 12:52               ` Martyn Jago
2012-03-27 20:34                 ` Aurélien Aptel
2012-03-27 21:22                   ` Achim Gratz
2012-03-27 22:11                     ` Aurélien Aptel
2012-03-28  6:34                       ` Achim Gratz
2012-03-29 17:50                         ` Aurélien Aptel
2012-03-29 17:52                           ` Samuel Wales
2012-03-29 19:04                           ` Achim Gratz
     [not found]               ` <87vclsykl6.fsf-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2012-03-27 20:03                 ` Aurélien Aptel
2012-03-26 16:01             ` Bastien
     [not found]               ` <87wr674aii.fsf-mXXj517/zsQ@public.gmane.org>
2012-03-27 20:49                 ` Aurélien Aptel
2012-03-27 22:10                   ` Bastien
2012-03-26 15:53     ` Bastien
  -- strict thread matches above, loose matches on Subject: below --
2012-03-21 18:51 Aurélien Aptel
2012-03-21 19:32 ` Aurélien Aptel
2012-03-21 19:34 ` Samuel Wales
2012-03-22 12:22 ` Thorsten
2012-03-24  8:16 ` Nicolas Goaziou
2012-03-26 16:03 ` 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:
  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=CAJ+Teof96icFpJdEgbMiZssUdgN7MTUUiQM+uW3pnv44SZGoJg@mail.gmail.com \
    --to=rustompmody@gmail.com \
    --cc=aurelien.aptel@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=ragel-users@complang.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).