From: Diego Zamboni <email@example.com> To: firstname.lastname@example.org Cc: emacs-orgmode <email@example.com> Subject: Re: Using backticks for the inline code delimeter? Date: Wed, 31 Mar 2021 22:31:09 +0200 [thread overview] Message-ID: <CAGY83EfakT4080QQBvV2Ex-SxtYH_pJR9ywaTgXp--jeFdShsQ@mail.gmail.com> (raw) In-Reply-To: <CA+pajWJ99Vsb1VDTnJg9KquzeY=05T16B9bRdHXTKTjLQcfAYw@mail.gmail.com> [-- Attachment #1: Type: text/plain, Size: 1345 bytes --] The approach I've taken is to try and stop using Markdown altogether and write everything in Org, exporting to Markdown for those destinations that need it. You could even use https://github.com/tecosaur/org-pandoc-import to automatically convert/reconvert other formats as needed, and https://github.com/tecosaur/emacs-everywhere to do it even in other applications. It's not perfect - I still have to type Markdown sometimes, but you can eventually start losing the ingrained backtick habit :) --Diego On Wed, Mar 31, 2021 at 8:49 PM George Mauer <firstname.lastname@example.org> wrote: > Markdown uses backticks to denote inline code which should get special > (typically monospace) formatting, org uses the tilde character. > > Now I know that org is not markdown, is far more powerful than markdown, > and is not (mostly) the same use cases as markdown. But this one use case > *does* overlap. And the backticks thing is becoming so ingrained that not > only do I reach for it all the time, but I've seen it crop up on this very > mailing list and even in some README.org documents. > > I would like to submit that org consider adopting backticks as an > alternate way of denoting inline code. > > Aside from any official movement, I would like to add this to my own files > - is there a straightforward way to extend the org parser to do this? > [-- Attachment #2: Type: text/html, Size: 1950 bytes --]
next prev parent reply other threads:[~2021-03-31 20:32 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 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 [this message] 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 \ --in-reply-to=CAGY83EfakT4080QQBvV2Ex-SxtYH_pJR9ywaTgXp--jeFdShsQ@mail.gmail.com \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --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).