Re: Using backticks for the inline code delimeter?

[Bill Burdick]

Grepping for src_ in *.el in the org distro shows 11 hits over 3 files: ob-core.el, ob-exp.el, and org-element.el. That's where you can start working if you want to copy those functions into your init files and modify them for yourself, or you can see if maybe using function advice is sufficient.

It's your emacs config, you can modify it however you want, if what you want is to write the code yourself.

If you want someone else to write the code for you, however, you'll have to convince someone to do it.

If you want someone else to write the code for you and also adopt it into the main distro, that's an even tougher task...

-- Bill

On Wed, Mar 31, 2021 at 1:50 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?