From: David Masterson <email@example.com> To: Tim Cross <firstname.lastname@example.org> Cc: email@example.com Subject: Re: Empty headline titles unsupported: Bug? Date: Wed, 26 May 2021 16:37:39 -0700 [thread overview] Message-ID: <SJ0PR03MB5455D9327E7F2050AB0CF3B39B249@SJ0PR03MB5455.namprd03.prod.outlook.com> (raw) In-Reply-To: <firstname.lastname@example.org> (Tim Cross's message of "Wed, 26 May 2021 09:06:36 +1000") Tim Cross <email@example.com> writes: > David Masterson <firstname.lastname@example.org> writes: >> But having undefined behaviors is limiting on the portability of Org >> because people are unwilling to pick it up and attempt to (say) create a >> (partial) Org for other platforms (iPhone, Android, etc.). > This is very much a secondary consideration. While making it as easy as > possible to parse org files outside of Emacs is not a bad thing, it > should not be a primary driver for how org works. Org is an emacs mode > and I think we need to be careful when considering limiting what you can > do with it based on how easily it can be formally specified for external > tools to use. I think few org users would welcome a change which removed > a feature or required them to modify their workflow just to support the > development of non-emacs tools. Could it be done via a secondary parser? That is, define a base level language for Org that fits into a BNF (or..?) grammar and then a package that could be a pre-hook to the parser that rewrites improper tidbits into a grammatically correct form? I'm thinking, if the grammar is well defined, the secondary parser won't be that complex. -- David Masterson
next prev parent reply other threads:[~2021-05-27 0:06 UTC|newest] Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-22 11:15 Sebastian Miele 2021-05-22 12:21 ` Nicolas Goaziou 2021-05-23 4:45 ` Ihor Radchenko 2021-05-23 14:06 ` Nicolas Goaziou 2021-05-23 14:33 ` Ihor Radchenko 2021-05-23 14:55 ` Nicolas Goaziou 2021-05-23 15:22 ` Ihor Radchenko 2021-05-24 11:01 ` Sebastian Miele 2021-05-24 10:37 ` Sebastian Miele 2021-09-26 9:04 ` Bastien 2021-09-26 23:47 ` Tom Gillespie 2021-09-27 19:59 ` Nicolas Goaziou 2021-09-29 11:26 ` Bastien 2021-05-24 10:46 ` Sebastian Miele 2021-05-24 22:17 ` David Masterson 2021-05-25 10:43 ` Sebastian Miele 2021-05-25 11:43 ` Sebastian Miele 2021-05-25 16:10 ` Nicolas Goaziou 2021-05-25 21:04 ` David Masterson 2021-05-25 23:06 ` Tim Cross 2021-05-26 23:37 ` David Masterson [this message] 2021-05-26 14:07 ` Ihor Radchenko 2021-05-26 23:42 ` David Masterson 2021-05-27 3:29 ` Ihor Radchenko 2021-05-27 22:35 ` David Masterson 2021-05-28 5:36 ` Tom Gillespie 2021-05-29 6:21 ` David Masterson 2021-05-29 6:54 ` Tom Gillespie 2021-05-29 8:04 ` Ihor Radchenko 2021-05-29 19:33 ` Tom Gillespie 2021-05-30 4:06 ` Ihor Radchenko 2021-05-29 14:09 ` Ihor Radchenko 2021-05-30 2:19 ` David Masterson
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=SJ0PR03MB5455D9327E7F2050AB0CF3B39B249@SJ0PR03MB5455.namprd03.prod.outlook.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Empty headline titles unsupported: Bug?' \ /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).