This should be an easy plugin. I’d love an even quicker way to enter internal links: in addition to double-brackets I’d like it to recognize any WikiWord, which is a word with leading Caps and at least one internal Cap. I realize this isn’t to everyone’s taste, but I like it much better than double-brackets on every link.
I fits my brain to give my pages “CodeWords” that look like that, and it’s four characters less typing. I know this is essentialy the same argument as @ links like @page. But it’s an optional plugin so nobody has to use it if they don’t like it.
1 Like
Thanks, I was going to post the same 
Aka CamelCase
Users of dokuwiki know the easy way of creating links: camelcase [DokuWiki]
It would be nice to have the input of a plugin-dev in this one!
I guess it would be an easy one to trigger the wiki-brackets when canelcase is used. But leaving the CamelCase as is and display and make it behave as if it were a real link would require a feature request to be implemented in core obsidians I guess
The reason triggering wiki-brackets on all CamelCase words isn’t an ideal solution is because there will be some CamelCase words that the user does NOT want to be a link. If those words simply change color but would link to a new empty note it will not disrupt the flow of reading. But if those unintended CamelCase words get [[brackets]] added to them it would interrupt the flow of reading more.
The ultimate solution would be for each CamelCase word to check if there exists a note named CamelCase and then color highlight the CamelCase word as a link. If there is no existing note, don’t highlight the word. If the user control-enter or clicks on the word it would still create a new empty note so it is in fact an active link, it just isn’t highlighted as such until there is a note.