emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Peter Frings <peter.frings@agfa.com>
Cc: Rainer Stengele <rainer.stengele@diplan.de>,
	emacs-orgmode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Formal description of Org files
Date: Fri, 15 Apr 2011 14:05:55 +0200	[thread overview]
Message-ID: <88D992AF-EA32-4B53-878C-FC27A56DE9D9@gmail.com> (raw)
In-Reply-To: <71B98092-E488-4521-B545-4C3E4973D29C@agfa.com>


On Apr 15, 2011, at 1:50 PM, Peter Frings wrote:

> 
> On 15 Apr 2011, at 12:57, Carsten Dominik wrote:
> 
>> On Apr 15, 2011, at 10:54 AM, Rainer Stengele wrote:
>> 
>>> Am 15.04.2011 09:58, schrieb Carsten Dominik:
>>>> Hi,
>>>> 
>>>> I have a question.
>>>> 
>>>> At FOSDEM, someone asked me if there was a formal description of the structure of Org files, in some language that would be the input for a parser (or parser generator?) so that Org file could be easily parsed.
> 
> <snip>
> 
>>> Hi,
>>> 
>>> maybe Backus-Naur was meant?
>> 
>> That is very well possible.  Sounds like a word I would not have recognized....
>> So would on Org-mode grammar start like this?
> 
>> headline> ::= "*"+ <opt-todo-keyword>
>>                   <opt-priority-cookie>
>>                   <title>
>>                   <opt-tags>
>> 
>> <opt-todo-keyword> ::= <whitespace> <todo-keyword> | “”
> <snip>
> 
> Yes, that seems like extended BN. [1]
> Good luck with it! You’ll need it... :-)

Well, if tis is complicated, I am not going to do this.
But maybe there is a volunteer out there - I'd be happy to
support him or her.

- Carsten

  reply	other threads:[~2011-04-15 12:06 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-15  7:58 Formal description of Org files 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 [this message]
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:00               ` Searching the org list (was: Formal description of Org files) Memnon Anon
2011-07-16 18:21               ` Formal description of Org files 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
  -- strict thread matches above, loose matches on Subject: below --
2011-04-15 17:13 Rustom Mody
2011-04-15 17:27 ` MidLifeXis at PerlMonks
2014-09-21 12:10 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
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

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=88D992AF-EA32-4B53-878C-FC27A56DE9D9@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=peter.frings@agfa.com \
    --cc=rainer.stengele@diplan.de \
    /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).