This is the default behavior. So ~C-h f~ will show up as `C-h f` and then <code>C-h f</code> in the final Hugo generated HTML. Example: Few of Emacs help keybindings: C-h f, C-h v

Here the Org code markup is explicitly specified to be used for <kbd> tag generation by setting EXPORT_HUGO_USE_CODE_FOR_KBD property to t. So ~C-h f~ will show up as <kbd>C-h f</kbd>. Example: Few of Emacs help keybindings: C-h f, C-h v

Note that to disable the code fence option, the value portion of the property needs to be left empty instead of setting to nil! :PROPERTIES: :EXPORT_HUGO_CODE_FENCE: :END: Here are few variables that you might like to change in the local.mk: prefix: Org installation directory prefix = /dir/where/you/want/to/install/org # Default: /usr/share The .el files will go to $(prefix)/emacs/site-lisp/org by default. If you’d like to change that, you can tweak the lispdir variable.

foo1 foo2 bar1 bar2 baz1 baz2 zoo1 zoo2 numbered1 numbered2

You need to force end of list when you have something like an unordered list immediately following an ordered list. The easiest and cleanest way to do that is adding a comment between those lists. – Reference That would be the implementing in the Org exporter backend. But in Org, two consecutive blank lines after a list ends the list. In the below example, the foo* items would be in a different <ul> element than the bar* items.

Inline equations are wrapped between \( and \). $ wrapping also works, but it is not preferred as it comes with restrictions like “there should be no whitespace between the equation and the $ delimiters”. So $ a=b $ will not work (it will look like: $ a=b $), but $a=b$ will work (it will look like: \(a=b\)). On the other hand, both \(a=b\) (it will look like: \(a=b\)) and \( a=b \) (it will look like: \( a=b \)) will work.

Below table shows the translation of Org markup to Markdown markup in the exported .md files. Org Markdown In Hugo rendered HTML *bold* **bold** bold /italics/ _italics_ italics =monospace= `monospace` monospace ~key-binding~ `key-binding` key-binding - if org-hugo-use-code-for-kbd is nil [default] ~key-binding~ <kbd>key-binding</kbd> - if org-hugo-use-code-for-kbd is non-nil - Requires CSS to render the <kbd> tag as something special.

Note that to disable the “use code for kbd” option, the value portion of the property needs to be left empty instead of setting to nil! :PROPERTIES: :EXPORT_HUGO_USE_CODE_FOR_KBD: :END: Here ~C-h f~ will show up as `C-h f` in Markdown and then <code>C-h f</code> in the final Hugo generated HTML. Example: Few of Emacs help keybindings: C-h f, C-h v

The source blocks are code-fenced by default. Here are few variables that you might like to change in the local.mk: prefix: Org installation directory prefix = /dir/where/you/want/to/install/org # Default: /usr/share The .el files will go to $(prefix)/emacs/site-lisp/org by default. If you’d like to change that, you can tweak the lispdir variable. infodir: Org Info installation directory. I like to keep the Info file for development version of Org in a separate directory.

This case is not affected by Blackfriday Issue #239 as the fenced code block does not have Markdown syntax lists. List item 1 *abc*/def/=def= List item 2