emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Bastien <bzg@altern.org>
Cc: nicholas.dokos@hp.com,
	emacs-orgmode mailing list <emacs-orgmode@gnu.org>,
	Marcelo de Moraes Serpa <celoserpa@gmail.com>,
	Carsten Dominik <carsten.dominik@gmail.com>
Subject: Re: Formal description of Org files
Date: Sat, 16 Jul 2011 13:09:03 -0400	[thread overview]
Message-ID: <32582.1310836143@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bastien <bzg@altern.org> of "Sat, 16 Jul 2011 18:56:18 +0200." <87aacew4el.fsf@gnu.org>

Bastien <bzg@altern.org> wrote:

> Hi Marcelo,
> 
> Marcelo de Moraes Serpa <celoserpa@gmail.com> writes:
> 
> > I'm creating a web app that interacts with orgmode files and allows
> > you to edit orgmode files on the browser. The edit part is not done.
> 
> Wow, this would be a really useful tool.  Can't wait to test this!
> 
> > I'm quite good at Javascript, and I wouldn't mind hacking something
> > akin to orgmode elisp code and this will be what I'll do if
> > everything else fails, but wouldn't using a grammar be a cleaner and
> > more elegant solution?
> 
> Can you tell more about what you mean by "grammar"?
> 

A formal grammar of some sort I presume: BNF or EBNF.

> Back in february, at FOSDEM, someone asked for a description of the
> org-mode format specification.  This is still something that needs to be
> done.  Any stab at this (on Worg) would be really nice.  You can start
> anywhere (headlines, TODO keywords, etc.)
> 
> If the "grammar" needs to be described in a specific format (more than
> just a formal description of the various syntactic elements of an Org
> file), let us know.
> 

There was a discussion about this on the list a few months ago, but I
can't get to search.gmane.org to find the thread atm, although I can get
to news.gmane.org: is that me or is gmane's search on the fritz?

Nick

  reply	other threads:[~2011-07-16 17:09 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
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 [this message]
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=32582.1310836143@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=bzg@altern.org \
    --cc=carsten.dominik@gmail.com \
    --cc=celoserpa@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).