Org mode: Use Code (~) marker instead of Verbatim (=) for code

[khaalidrafi]

Pandoc always uses the Verbatim (=) marker in Org mode for code markers, such as the Markdown code (`) marker. But, Org mode has a special marker for Code (~). Verbatim (=) is simply meant to be used for text that isn't code but should ignore Org mode marker.

[jgm]

Since markdown inline backticks can be used for anything, it is hard to determine whether ~ or = is appropriate in the given case. Currently we use = for everything. Is there actually any important difference in how Org treats these?

[khaalidrafi]

* jgm left a comment (jgm/pandoc#11655) Since markdown inline backticks can be used for anything, it is hard to determine whether ~ or = is appropriate in the given case.

Yes. But, according to [Markdown doc](https://daringfireball.net/projects/markdown/syntax#code), (`) is supposed to be used for code. If people use the code marker for something else, that's upon them. We should use the equivalent Org marker for code here. Or, you may let users choose which one to use for this. And, I guess the Verbatim (=) marker of Org doesn't have any equivalent in most other markup formats.

Is there actually any important difference in how Org treats these?

I found some links online about this: 1. https://stackoverflow.com/questions/18991981/difference-between-code-and-verbatim-in-org-mode 2. https://irreal.org/blog/?p=11123

[jgm]

Backticks in Markdown are routinely used for things that aren't really code: file paths, package names, etc.

But from what I can see, it makes very little difference whether one uses ~ or = in Org. I think sticking with the current behavior is the best path.

[khaalidrafi]

Yes, code (`) maybe used for different stuffs, but since it is named the Code marker in Markdown docs, I think Code (~) should be used in Org, too. If you don't want to change that, I'd appreciate an option to choose between ~ or =. Yes, not a big deal at the moment. But, there are slight differences in exporting behavior in Emacs. Also, as Irreal notes, it might become an issue in future.