emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: David Masterson <dsmasterson92630@outlook.com>
To: "Jakob Schöttl" <jschoett@gmail.com>
Cc: Tom Gillespie <tgbugs@gmail.com>, emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: A formal grammar for Org
Date: Tue, 01 Jun 2021 21:00:33 -0700	[thread overview]
Message-ID: <SJ0PR03MB5455960FB0773F0C057CEE4A9B3D9@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw)
In-Reply-To: <13899acc-0760-a772-67d0-50b91cc5d9ac@gmail.com> ("Jakob Schöttl"'s message of "Tue, 1 Jun 2021 23:22:38 +0200")

Jakob Schöttl <jschoett@gmail.com> writes:

> Am 01.06.21 um 11:53 schrieb Tom Gillespie:
>>
>>> We have a pretty similar project, org-parser[1]. It's also written
>>> in a Lisp dialect, Clojure, but it uses instaparse instead of brag
>>> as parser library.
>> https://github.com/tgbugs/laundry/tree/next#similar-projects I managed
>> to get it into my README as a reminder to myself to have a thorough
>> look at it, but have been occupied with other work since then.
> Thanks, I'll also set a link in our README to related work.

Have either (or both) of you looked at BeOrg (http://beorg.app)?  This
is an (iOS) app that implements task management from Org files by
reading and updating the Org file structure.  I would assume it uses a
parser to breakdown the Org file structure and rebuild it later.  That
is what I see your parsers becoming.

-- 
David Masterson


  reply	other threads:[~2021-06-02  4:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d354da93-c910-c7c8-8bb5-51c3877575f9@gmail.com>
2021-06-01  9:53 ` A formal grammar for Org Tom Gillespie
2021-06-01 21:22   ` Jakob Schöttl
2021-06-02  4:00     ` David Masterson [this message]
2021-06-02  8:22       ` Jakob Schöttl
2021-06-03  2:36         ` David Masterson
2021-06-03 20:32         ` Jean Louis
2021-04-04  6:11 Tom Gillespie

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=SJ0PR03MB5455960FB0773F0C057CEE4A9B3D9@SJ0PR03MB5455.namprd03.prod.outlook.com \
    --to=dsmasterson92630@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=jschoett@gmail.com \
    --cc=tgbugs@gmail.com \
    /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).