From: Timothy <email@example.com> To: org-mode-email <firstname.lastname@example.org>, email@example.com Subject: Org Syntax Specification Date: Mon, 10 Jan 2022 02:02:34 +0800 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) [-- Attachment #1.1: Type: text/plain, Size: 2554 bytes --] Hi All, I’ve talked about adding citation syntax to the org-syntax document before, and previously expressed the thought that it could be generally improved quite a bit. This has culminated me in spending the last few days straight working on a rewrite of org-syntax.org to try to bring it closer to the point where we can knock “(draft)” out of the title 🙂. Ihor has been a tremendous help pointing out inaccuracies and explaining some of the parsing behaviour (thanks!), which has allowed me to get it to a point where I think it would benefit from wider feedback. I’ve just pushed my latest revision to worg as <https://orgmode.org/worg/dev/org-syntax-edited.html>. Personally though, I think it’s best viewed as a PDF, so I’ve also uploaded the PDF export to <https://0x0.st/oiM5.pdf>. It would be great if those of you with an interest/understanding of Org’s syntax could have a look and let me know what you think. I think the best way to compare to the current org-syntax.org would be to put them side-by-side. I’ve attempted to list the main changes I’ve made in the appendix, however I’ve likely missed things. Lastly, having spent a while looking at the syntax, I’m wondering if we should take this opportunity to mark some of the syntactic elements we’ve become less happy with as *(depreciated)*. I’m specifically thinking of the TeX-style LaTeX fragments which have been a bit of a pain. To quote Nicolas in org-syntax.org: It would introduce incompatibilities with previous Org versions, but support for `$...$' (and for symmetry, `$$...$$') constructs ought to be removed. They are slow to parse, fragile, redundant and imply false positives. — ngz Marking this as depreciated would have no effect on Org’s current behaviour, but we could: 1. Mark as depreciated now-ish 2. Add a utility to convert from TeX-style to LaTeX-style 3. Add org lint/fortification warnings 4. A while later (half a decade? more?) actually remove support The other component of the syntax which feels particularly awkward to me is source block switches. They seem a bit odd, and since arguments exist, completely redundant. ―――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――――― That’s all for now, I hope you all had a great Christmas and new year! All the best, Timothy [-- Attachment #1.2: Type: text/html, Size: 7068 bytes --]
next reply other threads:[~2022-01-09 18:26 UTC|newest] Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-01-09 18:02 Timothy [this message] 2022-01-15 12:40 ` Sébastien Miquel 2022-01-15 16:36 ` Depreciating TeX-style LaTeX fragments (was: Org Syntax Specification) Timothy 2022-01-16 8:08 ` Sébastien Miquel 2022-01-16 9:23 ` Depreciating TeX-style LaTeX fragments Martin Steffen 2022-01-16 9:46 ` Colin Baxter 😺 2022-01-16 11:11 ` Tim Cross 2022-01-16 13:26 ` Juan Manuel Macías 2022-01-16 14:43 ` Colin Baxter 😺 2022-01-16 15:16 ` Greg Minshall 2022-01-16 17:45 ` Rudolf Adamkovič 2022-01-16 12:10 ` Eric S Fraga 2022-01-16 14:30 ` Anthony Cowley 2022-01-18 0:54 ` Org Syntax Specification Tom Gillespie 2022-01-18 12:09 ` Ihor Radchenko 2022-01-19 1:22 ` Tom Gillespie 2022-01-19 11:58 ` 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 \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Org Syntax Specification' \ /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).