From: Tim Cross <email@example.com> To: firstname.lastname@example.org Subject: Re: Using backticks for the inline code delimeter? Date: Fri, 02 Apr 2021 11:28:28 +1100 [thread overview] Message-ID: <email@example.com> (raw) In-Reply-To: <firstname.lastname@example.org> Joost Kremers <email@example.com> writes: > On Fri, Apr 02 2021, Tim Cross wrote: >> Getting backticks to font-lock correctly is relatively easy. Getting the >> exporters to understand the new syntax is more of a challenge > > Don't the exporters work off of some intermediate representation, like Pandoc > does? I kinda thought that was what `org-element.el` was all about... > > And of course I meant to type ~org-element.el~ there... :D Yes, at least most of the core ones should. However, I would still expect some surprises and of course there are no guarantees regarding the contrib and other external ones. Despite attempts to abstract the syntax to make it 'flexible', I would be surprised if there is not functionality in some of the exporters which has implicit assumptions regarding the syntax being used and is not isolated from such changes. Note that I'm not saying this cannot be done or even that is should not be done. I just want to highlight that just making changes to how org deals with it at the 'presentation' layer may not be sufficient and that you would have to verify there are no unexpected side effects in any of the exporters. If you wanted to keep backwards compatibility or make using ` and alternative to ~, you would also need to decide/verify things like `word~ (i.e. mixed delimiters) are handled correctly (i.e. simple regex with alternatives would not be sufficient - would need to be a match which allowed both but ensured matching values). Of course, there is a big difference between making a change to org and making a change to an individual's own org instance. So if we are talking about how someone can hack their own org instance to use ` instead of ~, it can be much simpler as they don't have to worry about the bits they don't use or backwards compatibility. The downside then becomes just the hassle of maintaining your hacks over subsequent org releases. One reason why I would probbly go with a method which just changes how I input data. For example, I would define a function which inserts ~ or if a region is marked, surrounds it in ~ and then just bind that to a key, never using ~ or ` directly to mark text. -- Tim Cross
next prev parent reply other threads:[~2021-04-02 1:02 UTC|newest] Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-03-31 18:48 George Mauer 2021-03-31 19:16 ` autofrettage 2021-03-31 19:19 ` Timothy 2021-04-01 6:03 ` Marcin Borkowski 2021-04-20 13:30 ` Matt Price 2021-04-20 20:24 ` John Kitchin 2021-04-21 22:37 ` Matt Price 2021-04-20 22:30 ` Tim Cross 2021-04-21 19:22 ` John Kitchin 2021-04-21 19:49 ` Tim Cross 2021-03-31 19:24 ` Sébastien Miquel 2021-04-01 16:49 ` Maxim Nikulin 2021-04-01 17:05 ` Timothy 2021-04-01 18:43 ` Samuel Wales 2021-04-01 23:14 ` Tim Cross 2021-04-01 23:30 ` Joost Kremers 2021-04-02 0:28 ` Tim Cross [this message] 2021-04-04 1:13 ` Tom Gillespie 2021-04-04 10:03 ` Joost Kremers 2021-04-04 12:19 ` Nicolas Goaziou 2021-04-04 16:46 ` Bill Burdick 2021-04-04 17:24 ` Nicolas Goaziou 2021-04-04 19:33 ` Joost Kremers 2021-04-04 23:06 ` Nicolas Goaziou 2021-04-06 15:03 ` Maxim Nikulin 2021-04-19 9:27 ` Nicolas Goaziou 2021-03-31 19:28 ` Timothy 2021-03-31 19:55 ` autofrettage 2021-03-31 20:31 ` Diego Zamboni 2021-03-31 21:51 ` George Mauer 2021-03-31 22:27 ` Dr. Arne Babenhauserheide 2021-03-31 22:38 ` Tim Cross 2021-04-01 0:25 ` Samuel Wales 2021-04-01 1:11 ` Bill Burdick 2021-04-01 3:42 ` Greg Minshall 2021-04-01 9:32 ` autofrettage 2021-04-02 11:23 ` Andreas Eder 2021-04-04 17:06 ` Maxim Nikulin 2022-03-19 3:17 chris 2022-03-19 3:24 ` chris
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Using backticks for the inline code delimeter?' \ /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).