emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Gustav Wikström" <gustav.erik@gmail.com>
To: "Gustav Wikström" <gustav.erik@gmail.com>,
	"Org Mode List" <emacs-orgmode@gnu.org>
Subject: Re: Formal description of Org files
Date: Sat, 4 Oct 2014 21:49:33 +0200	[thread overview]
Message-ID: <CA+SyOP-B7cvi_hsCe23GgzoPH-Gp89eWzY1rnoJfG+3Ai_q+hA@mail.gmail.com> (raw)
In-Reply-To: <87ha0187pc.fsf@nicolasgoaziou.fr>

Ah, yes. I've seen that and I really really admire your work. :-) What
I'm aiming at is something more standardised. Something that can be
used to generate language lexers and parsers in other programming
languages.. But, as I stated a moment ago in another mail to the list
- I don't really know the power of such a standardised grammar and of
what can be done if it was there.. I only envision the possibilities.
;-)

Best regards
Gustav

On Sun, Sep 21, 2014 at 2:43 PM, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,
>
> Gustav Wikström <gustav.erik@gmail.com> writes:
>
>> There was a discussion many years back about a formal description of
>> Org files [1]. In some way that might be achieved now in org-elements,
>> but that still is heavily bound to elisp.
>>
>> So my question is; have there been more discussions of constructing
>> such a formal grammar? Maybe in EBNF form. I suspect getting every
>> aspect of Org mode into such a description would be difficult. But
>> imagine the possibilities. Tools such as ANTLR and similar would
>> straight away have a way of parsing Org mode. Org mode source files
>> could be parsed in many other languages, simplifying the process of
>> expanding Org mode to other platforms ( Android & iOS, web ).
>>
>> Further rant; To me Org mode should be less about Emacs and more about
>> the source file format. Let Emacs be the main carrier, but let Org
>> mode also expand into other domains. One way to simplify this might be
>> to provide the formal description so that other tools might be easier
>> to develop based on this grammar.
>>
>> (For me, the biggest limitation of Org mode is lacking tools to
>> utilize it on the run. The aim of this is thus to feed thoughts on how
>> to simplify processes that can expand Org mode into those "more
>> mobile" domains).
>
> See
>
>   (info "(org) Org syntax")
>
>
> Regards,
>
> --
> Nicolas Goaziou

  parent reply	other threads:[~2014-10-04 19:49 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-21 12:10 Formal description of Org files Gustav Wikström
2014-09-21 12:43 ` Nicolas Goaziou
2014-10-02  8:28   ` Samuel Loury
2014-10-02 17:03     ` Nicolas Goaziou
2014-10-04 19:49   ` Gustav Wikström [this message]
2014-09-26  8:12 ` Eric S Fraga
2014-09-26 12:53   ` Grant Rettke
2014-09-26 20:51     ` Eric S Fraga
2014-10-04 19:41   ` Gustav Wikström
2014-10-06 14:22     ` Samuel Loury
  -- strict thread matches above, loose matches on Subject: below --
2011-04-15 17:13 Rustom Mody
2011-04-15 17:27 ` MidLifeXis at PerlMonks
2011-04-15  7:58 Carsten Dominik
2011-04-15  8:54 ` Rainer Stengele
2011-04-15 10:57   ` Carsten Dominik
2011-04-15 11:50     ` Peter Frings
2011-04-15 12:05       ` Carsten Dominik
2011-04-15 15:25         ` Jambunathan K
2011-04-20 11:57           ` Olaf.Hamann
2011-04-15 12:58 ` Christian Egli
2011-04-15 13:42   ` Peter Frings
2011-04-15 13:52     ` Filippo A. Salustri
2011-04-15 14:20 ` Wes Hardaker
2011-04-15 17:29   ` Eric Schulte
2011-04-15 18:31     ` Nick Dokos
2011-04-20 12:37       ` Olivier Schwander
2011-07-15 18:07         ` Marcelo de Moraes Serpa
2011-07-16 16:56           ` Bastien
2011-07-16 17:09             ` Nick Dokos
2011-07-16 17:12               ` Bastien
2011-07-16 18:21               ` suvayu ali
2011-07-16 18:43                 ` Nick Dokos
2011-07-17 23:14             ` Eric Schulte
2011-07-18  9:30               ` Christopher Witte
2011-07-18 23:32               ` Bastien
2011-07-18 21:02             ` Marcelo de Moraes Serpa
2011-07-18 21:03               ` Marcelo de Moraes Serpa
2011-07-18 11:04           ` Nicolas Goaziou
2011-07-18 23:35             ` Bastien
2011-07-19  6:16             ` Jambunathan K
2011-07-24 18:58               ` 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=CA+SyOP-B7cvi_hsCe23GgzoPH-Gp89eWzY1rnoJfG+3Ai_q+hA@mail.gmail.com \
    --to=gustav.erik@gmail.com \
    --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).