Re: Using backticks for the inline code delimeter?

[Diego Zamboni]

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 <gmauer@gmail.com> 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?