Open in TheBrain

Markdown inline styling

Conversation with Gemini

In TheBrain 15, that "sometimes it works, sometimes it doesn't" frustration usually comes down to a specific behavior in how the new note editor parses Markdown inline styling.

When you use the backtick syntax (term), you are telling the editor to format that text as inline code. Here is the exact procedure for how the editor handles it, why adding them after the fact is failing for you, and how to fix it.

The Trigger: It Needs a "Space" to Activate

The editor uses an "auto-convert" or "live markdown" engine. It triggers the formatting the exact moment you type the closing backtick followed by a space or punctuation.

When typing fresh:

If you type my term and then hit the Spacebar, it instantly wraps into a grey code block.

Why editing existing text fails:

If you already have the word term on the screen, move your cursor to the front, type a backtick, move to the back, and type a backtick, the editor doesn't auto-parse it. It just sits there as literal backtick characters. It needs to detect that closing sequence dynamically.

The Correct Procedures

Depending on whether you are typing new text or fixing old text, use these steps:

If the term is already written on your screen, don't type the backticks manually.

Highlight/select the existing term with your mouse or keyboard (Shift + Arrow keys).

Press the backtick key (`) just once.

The editor will automatically wrap the selection with a backtick on both sides and instantly convert it into the proper inline code format.

If you prefer to type the backticks manually around existing text, you have to "trick" the parser into seeing a closing event:

💡 A Quick Note on TheBrain's Search: Just keep in mind that formatting a term as inline code changes how it looks visually in your note, but it doesn't alter how TheBrain's search indexing handles it. It will still show up in your global searches just like standard text.

Give that single-tic highlight shortcut a shot on your existing thoughts—it's usually the cleanest workaround for the v15 editor quirk!