From: Greg Minshall <minshall@umich.edu>
To: Tom Gillespie <tgbugs@gmail.com>
Cc: Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: did behaviour of RET change again?
Date: Thu, 24 Dec 2020 06:34:47 +0300 [thread overview]
Message-ID: <505431.1608780887@apollo2.minshall.org> (raw)
In-Reply-To: Your message of "Wed, 23 Dec 2020 18:09:15 -0500." <CA+G3_PO1p-QNGG3vf+8eZ8bG1NQH77NH7y51=knm9s3yUPwveA@mail.gmail.com>
Tom,
> The other reason I think this is a good idea is because I have been
> working on a formal grammar for the org syntax, and everything would
> be SO much simpler about the implementation after the first pass parse
> if the canonical representation of an Org file did not allow
> significant whitespace (with an exception for plain lists).
possibly i'm misunderstanding, but my sense is that the value of org
adapt indentation doesn't change what you might actually find ("in a
.org file in the wild"). so, whatever its value, your grammar would
have to deal with all cases?
or, and maybe this would make sense, you'd define an "interoperability"
form of .org, that all "wild" .org files could be (programmatically)
converted into, without losing any of their semantics?
(anyway, good luck with that, even with any significant subset of that!)
cheers, Greg
next prev parent reply other threads:[~2020-12-24 3:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-18 13:06 did behaviour of RET change again? Eric S Fraga
2020-12-18 14:42 ` Pankaj Jangid
2020-12-18 14:59 ` Eric S Fraga
2020-12-19 4:21 ` Pankaj Jangid
2020-12-18 18:33 ` Berry, Charles via General discussions about Org-mode.
2020-12-20 17:25 ` Bastien
2020-12-20 18:56 ` Gustavo Barros
2020-12-21 8:46 ` Eric S Fraga
2020-12-21 10:25 ` Eric S Fraga
2020-12-21 11:34 ` Kévin Le Gouguec
2020-12-22 15:36 ` Kyle Meyer
2020-12-22 23:15 ` Samuel Wales
2020-12-22 23:25 ` Samuel Wales
2020-12-23 23:09 ` Tom Gillespie
2020-12-24 3:34 ` Greg Minshall [this message]
2020-12-24 6:35 ` Tom Gillespie
2020-12-25 6:29 ` Devin Prater
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=505431.1608780887@apollo2.minshall.org \
--to=minshall@umich.edu \
--cc=emacs-orgmode@gnu.org \
--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).