These two ways refer to a page with an alias for the link:
[[Obsidian|`obsidian`]]
[`obsidian`](Obsidian.md)
I would expect both links to render as obsidian (i.e. monospace code), but the wikilink renders as `obsidian`. (The Markdown link as obsidian.)
Would it be possible to add support for markup in wikilink aliases as well?
+1. You can put the markup outside the wiki link as in _[[page|title]]_, but that only works for bold and italic etc, but obviously not for monospace since monospace disables interpretation of what’s inside. Making backticks work for aliases would be fantastic (and hopefully not too hard to implement?)
+1+1 !
+1 I would also add the the solution @rab suggested affects the entire link and you can’t target a specific section with italics or bold: [[The TeXbook|Knuth's _The TeXbook_]]
+1. I would love to be able to have e.g. italics within display text.
+1, would love to see this implemented.
I’ve got a half-baked solution to styling an internal link as inline code. In Settings, go to Appearance > CSS snippets > Open snippets folder and add a file named code-link.css (or whatever you want) then paste the following contents:
.cm-formatting-code.cm-hmd-internal-link:has(
+ .cm-hmd-internal-link + .cm-formatting-code.cm-hmd-internal-link
) {
border-start-start-radius: var(--code-radius);
border-start-end-radius: 0;
border-end-start-radius: var(--code-radius);
border-end-end-radius: 0;
}
.cm-formatting-code.cm-hmd-internal-link
+ .cm-hmd-internal-link:has(+ .cm-formatting-code.cm-hmd-internal-link) {
font-family: var(--font-monospace);
font-size: var(--code-size);
background-color: var(--code-background);
padding: 0.1em 0;
border-radius: 0;
vertical-align: baseline;
-webkit-box-decoration-break: clone;
}
.cm-formatting-code.cm-hmd-internal-link
+ .cm-hmd-internal-link
+ .cm-formatting-code.cm-hmd-internal-link {
border-start-start-radius: 0;
border-start-end-radius: var(--code-radius);
border-end-start-radius: 0;
border-end-end-radius: var(--code-radius);
}
Make sure to hit Reload snippets and toggle it on.
It doesn’t work for certain links, it doesn’t hide the backticks, it doesn’t add spellcheck="false" to disable spellcheck, and it doesn’t work in Reading view. Here’s what it looks like:
Versus before:
(Edit: nesting :has() doesn’t work)
Need this!
+1 from me too.
I decide to temporarily use Markdown link so the code format would show, and painfully replace space with %20 individually. Three links only and it took forever 
Bump! I’d love this
+1 – still a wanted feature in August 2025.
i have been running into this issue for a full year now, thinking its some trivial oversight that will surely be addressed any minute now, a whole year and still the rendering is broken, come on. wiki links are super usefull in obisidian, not least, the auto rename feature, this issue is pretty much nullifying wiki links in my eyes.
This post has pointed out what I propose in the feature request. It was marked as a bug, which is not a bug, it’s just something Obsidian does not support. The moderator WhiteNoise said it is not supported.
The thing I would like is when you have an internal note that links to a header or an alias, the markdown render is applied. [[note|name]] would render name in live preview / read mode. Same for [[note#header]] would render header.
In my case, which is a bit specific, it would be very helpful. I often use Obsidian to make notes about source code. Some code bases have good documentation and other do not. Plus, let’s let aside the quality / complexity of the code base, those notes are very meaningful and useful as quick side notes “How to do this”, “A quick summary how I used this 1,000 lines module in a project” etc..
The result is that I name my file module.py (for a Python code) for example. Often, there is only one class in the module: MyClass. So I add an alias MyClass which I can refer in other note. Then I would like to directly link the alias. Another use case is when I have my note module.py, it might have multiple important classes. So I have header level 2 for each class. This is the same problem, if I link [[module.py#HeaderClass]], I do not have the Markdown render.
Enable markdown rendering for internal link if there is a header or an alias with markup format symbols (stars, back tick ..)
[[note|
name]] would rendernamein live preview / read mode. Same for [[note#header]] would renderheader.
I tried to do [[note|MyClass]], it does not work. The internal link is not even detected.
I have seen some feature request like this, which is about markdown rendering too but I do not think it’s related. I really tried to search for similar post and I did not find it. Plus I could not find link pointing to the bug post. I hope I did not make a duplicate.
Would it be possible to make math render in links? Essentially I am talking about the following displaying the rendered x at the last line and not $x$.
$$x = 10$$
^fftest
[[#^fftest|$x$]]
I am reading a lot of scientific papers with maths where variables all have some specific complicated meaning. With wikilinks I could use block referencing, such that when I type the variable and hover over I can see what it means. This would be great when the variable is a complicated expression.
Make math mode renderable in links? I don’t know if this is complicated or simple.
Right now I am defining the variable at the top of the note and then link the definition with block referencing to one of the other words in the text. For example
“… then we see that the [[#^fftest|$x$variable]] x is not identifiable…”
This is the closest I have found as a request. It is, however, the opposite direction of linking.. I think that what the person suggests might be really hard to implement in the latex environment but I hope that the reverse direction would be different.
I am not sure but is this similar?
Sometimes notes have an equation as title, and I’d like to show them as such in links.
If link alt name is defined and contains LaTex, render that LaTex part just like it’s rendered elsewhere in the document.
Please see this related bug report.
–
–
I would love that feature as well.
This works: [$NH_3$](ammonia)
This does not work: [[ammonia|$NH_3$]]
That is a very good workaround for now, I did not know that. Thank you!
Thanks!
The only downside is that it does not allow intervals.
This works:
> [$g(\tilde{S}_T, \mu_0 \mid \tilde{y}_{T})$](joint_conditional_disribution)
This does not:
[$g(\tilde{S}_T, \mu_0 \mid \tilde{y}_{T})$](joint conditional disribution)
That seems like a separate bug - can you file it?
