emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: David Masterson <dsmasterson92630@outlook.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Concerns about community contributor support
Date: Tue, 20 Apr 2021 09:46:25 +1000	[thread overview]
Message-ID: <87czup6d0u.fsf@gmail.com> (raw)
In-Reply-To: <DS7PR03MB54473C6353497B3BA54B52539B499@DS7PR03MB5447.namprd03.prod.outlook.com>


David Masterson <dsmasterson92630@outlook.com> writes:

> Tim Cross <theophilusx@gmail.com> writes:
>
>> I suspect the best model for moving forward is for new features and
>> enhancements to be initially implemented as add on contribution packages
>> rather than as extensions/enhancement to the core 'org-mode' package.
>> Such packages, if found to be popular or useful to a large number of
>> org-mode users could then be considered for inclusion as part of the
>> main org-mode package. The nature of elisp makes this type of model very
>> suitable as you can modify almost any aspect of org-mode via add on
>> packages in a consistent and stable manner and avoid impacting the core
>> functionality until the extension/enhancement has matured
>> sufficiently.
>
> What is the current status of having a BNF (or...?) parser for Org
> files?  In particular, the parser rules that could then be adopted by
> tools that use Org files on other systems (iPhone, Android, ...)?  Given
> the availability of parser generators (bison...), this would be good for
> breaking into smartphones where Emacs doesn't run.

While not BNF, Tom Gillespie has been working on documentation of the
org grammar as part of a broader objective to make it easier for other
external tools to parse org files. Below is a message he recently posted
to the list.

Note that I think this is a slightly different topic to the
development/maintenance of org-mode. The external packages I was
referring to are still Elisp based packages. Non-Elisp tools which can
parse and possibly edit org files would be a good thing for accessing
org files on other devices and outside of Emacs. However, such tools
will always be more limited because of the complexity of adding things
like multiple export formats, babel tangling of src blocks etc (most of
which was really only viable in Emacs because Emacs already had support
for much of that functionality - a subtle point of org mode often
overlooked is that what it primarily did was take existing Emacs
functionality and 'wrapped' it in a UI layer to provide a more
consistent and 'directed' interface to existing Emacs functionality).

 > From Tom Gillespie <tgbugs@gmail.com>

 > Dear all,
 >    Here is a draft of a formal grammar for Org mode [1]. It is still
 > in a rough state, despite quite a bit of work. However, following some
 > changes to improve performance for parsing real (big) Org files, I
 > think it is time to share it with the community so that we can start
 > to gather feedback. There are a number of opportunities that I have
 > found for simplifying the org grammar (sometimes by extending it to
 > make it more regular, and in the process adding useful features) that
 > are much easier to understand with this grammar in hand as a
 > reference. The grammar itself is implemented using Racket's #lang brag
 > (see [2] for an overview of brag's syntax). I had considered trying to
 > break it up into literate sections in an Org file, but for now decided
 > to leave it as a single file to simplify the development workflow. As
 > a result the full implementation is fairly long [3]. Comments and
 > feedback would be greatly appreciated. Best!
 > Tom
 
 > 1. https://github.com/tgbugs/laundry
 > 2. https://docs.racket-lang.org/brag/#%28part._.The_language%29
 > 3. https://github.com/tgbugs/laundry/blob/master/org-mode/parser.rkt
 
-- 
Tim Cross


  parent reply	other threads:[~2021-04-20  0:01 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-16 18:43 Timothy
2021-04-17 23:29 ` Thomas S. Dye
2021-04-18  1:56   ` Tim Cross
2021-04-18 19:39     ` Timothy
2021-04-18 22:45       ` Tim Cross
2021-04-19 21:43     ` David Masterson
2021-04-19 22:21       ` Gustav Wikström
2021-04-23  0:16         ` David Masterson
2021-04-19 23:46       ` Tim Cross [this message]
2021-04-20  8:21         ` Tom Gillespie
2021-04-23  0:34           ` David Masterson
2021-04-20  9:28       ` Jean Louis
2021-04-23  0:38         ` David Masterson
2021-04-18  5:04   ` Timothy
2021-04-18 18:45     ` Thomas S. Dye
2021-04-18 19:12       ` Timothy
2021-04-18 19:46         ` Thomas S. Dye
2021-04-18 19:59           ` Timothy
     [not found] ` <a64adc3de7be49039372851ea31e4f7c@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-19 10:04   ` Eric S Fraga
2021-04-20  3:54     ` Timothy
2021-04-19 22:07 ` Gustav Wikström
2021-04-21  9:33   ` Jean Louis
2021-04-21  9:50     ` Tim Cross
2021-04-21 10:25       ` Heinz Tuechler
2021-04-21 12:55         ` ian martins
2021-04-21 13:07         ` Timothy
     [not found]         ` <1c557c0e35e04440ba2dadfe57e5b590@VI1PR0102MB3327.eurprd01.prod.exchangelabs.com>
2021-04-21 13:27           ` Eric S Fraga
2021-04-21 15:31             ` ian martins
2021-04-21 15:38               ` Bruce D'Arcus
2021-04-21 19:35                 ` Tim Cross
2021-04-22  0:36                   ` ian martins
2021-04-22  0:48                     ` Tim Cross
2021-04-22  2:35                       ` Timothy
2021-04-22  5:14                         ` Maintaining babel packages — a list of packages that need help? Dr. Arne Babenhauserheide
2021-04-22 10:10                           ` ian martins
2021-04-26  7:25                           ` Bastien
2021-04-22 10:00                       ` Concerns about community contributor support ian martins
2021-04-21 19:31             ` Tim Cross
2021-04-25  4:30 ` Bastien
2021-04-25  5:52   ` Contributor Steward role (was Re: Concerns about community contributor support) Timothy
2021-04-25  7:13     ` Bastien
2021-04-25  6:17   ` Concerns about community contributor support Tim Cross
2021-04-25  7:19     ` Bastien
2021-04-26  0:23       ` Tim Cross
2021-04-26  5:00         ` Bastien
2021-04-26  6:07           ` Tim Cross
2021-04-26  7:34             ` Bastien
2021-04-25 10:10   ` Help with reproducing bugs reported on this list (was: Concerns about community contributor support) Bastien
2021-04-27  6:28     ` Help with reproducing bugs reported on this list Bastien
2021-04-25 21:40   ` Concerns about community contributor support Nick Savage
2021-04-26  7:22     ` Bastien
2021-04-29 14:07 ` D
2021-04-29 14:16   ` Bastien
2021-04-29 14:44     ` D
2021-04-29 14:29   ` Ihor Radchenko

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=87czup6d0u.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=dsmasterson92630@outlook.com \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Concerns about community contributor support' \
    /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

Code repositories for project(s) associated with this 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).