Repository navigation
Missing option to apply Markdown inline code formatting (single backticks `) in the editor #9076
Description
Nextcloud Text correctly renders inline code, but does not provide an option to apply inline code formatting in the editor.
For example, existing Markdown inline code such as inline code is correctly rendered when opening a Markdown file in Text, including in Collectives. However, there appears to be no way to apply inline code formatting to text directly in the editor, either through the toolbar or by typing single backticks (`).
- Markdown syntax is not properly rendered in text
- Markdown syntax is removed after closing text
- Markdown syntax is changed after closing text
- Something else: Please describe more in detail
When typing single backticks around text in the editor, they are treated as literal characters and automatically escaped in the resulting Markdown file (e.g., `inline code` instead of inline code). This behavior may be intentional for typing, but there should be an option in the editor's toolbar to apply inline code formatting to selected text.
Example markdown file
This text containing \`inline code\` has been typed in using the Nextcloud editor.
This text containing `inline code` has been written in an editor outside of Nextcloud.
Actual rendering in Nextcloud Text
This text containing `inline code` has been typed in using the Nextcloud editor.
This text containing inline code has been written in an editor outside of Nextcloud.
Expected behavior
Users should be able to apply inline code formatting to selected text directly in the editor, preferably through a toolbar option.
Details
- Nextcloud version: 34.0.3
Activity
[-]Markdown inline code input rule using backticks (`) is missing[/-][+]Cannot apply inline code formatting using backticks (`) in the editor[/+]Febulix commentedon Oct 14, 2026
I updated the issue description after some further testing to clarify the actual problem.
Initially, I assumed that Nextcloud Text wasn't rendering inline code correctly because typing backticks in the editor resulted in them being displayed as literal characters. However, I found that existing Markdown inline code is actually rendered correctly and that the editor simply escapes the backticks I type.
Therefore, this is probably more of an enhancement request than a bug report, as there seems to be no way to apply inline code formatting directly in the editor.
[-]Cannot apply inline code formatting using backticks (`) in the editor[/-][+]Missing option to apply Markdown inline code formatting (single backticks `) in the editor[/+]mejo- commentedon Oct 15, 2026
Dear @Febulix, thanks for your report. Inline code formatting is only applied after you type the second backtick. I.e. try typing backtick - some word - backtick. It should turn into an inline code element with "some word" in it. Does it work for you?
Febulix commentedon Oct 15, 2026
Thanks a lot for the reply, @mejo- !
You're absolutely right – it works if you type a backtick, enter the text, and then type the closing backtick. 👍
I think I even remember discovering this by accident at some point, but for some reason, I've gotten into the habit of typing both backticks first and then filling in the text between them. In that case, the text isn't recognized as inline code.
It also doesn't work with double backticks, which you need, for example, to display a backtick as code itself, like this:
`But I have to admit that it's debatable whether this is even a use case worth supporting. 😄
I always assumed that inline code formatting simply wasn't supported, since there's no menu item for it and I couldn't get it to work. So this doesn't seem to be a bug, but rather a UX issue.
I also eventually discovered, after a surprisingly long search, that the keyboard shortcuts Cmd ⌘ + E on macOS and Ctrl + E on Windows and Linux do the trick for selected text..
In my opinion, it would be nice to have a dedicated button for inline code formatting, just like the ones for highlighting, strikethrough, etc., with the keyboard shortcut shown in the tooltip. If not for the UX improvement itself, then at least for the sake of consistency. 😊