Create alias from selected text in target note frontmatter

Aliasing and switching back and forth between notes is creating a lot of friction, disrupting work in the current note.

Idea for a process:

Select text in current note
Open a menu “Set as alias for…”
Search for target note and hit Enter
The alias is created and the selected text is linked to the target note

Done. Continue working in current note.

Would this be possible?

Previously suggested:


Working links:
Automatic update aliases metadata
Add aliases to frontmatter by right click on a link with alias
Auto add pretty links to aliases - toggle

1 Like

I have since found two plugins that each do some part of what I am suggesting:

GitHub - mrjackphil/obsidian-crosslink-between-notes: This plugin adds a command which allows to add a link to the current note at the bottom of selected notes

Creates a backlink to the current note in a target note that is found through the quick switcher (without leaving the current note).

GitHub - hadynz/obsidian-sidekick: A companion to identify hidden connections that match your tags and pages

This plugin has the ability to just link the highlighted text in the current note (that it highlights itself through a constant search of existing notes).

Maybe these two parts could be adapted? Another aspect necessary would be a check whether the target note already has YAML frontmatter and whether the alias already exists?

1 Like

+1 !!! Woot!

Nay, + all-of-the-plusses!!!

And all of the nonplusses!!!

This is exactly the solution to one of the final frictional-inertia usefulness issues remaining in Obsidian, which restricts its value to the information-presentation mindset of knowledge-working-tool design (a la unidirectional hyperlinks in the webpages of yore) instead of the more information-creation mindset of working with information to create new knowledge.

Value to Create, not display.

Whatever the term: inline aliasing, annotation, defining, disambiguating, etc., the need is the same. An ability to further clarify meaning from message. While crafting (see, during creation) the message (and therefore its meaning) in realtime, not retrospectively. And certainly not at some future point, broken from flow, when picking out the color of the drapes while designing the webpage with which to present mere information, such is the pupal stage of knowledge’s growth.

In terms of biological development–explicitly–two data eggs exchanged their data → creating a new information larva → knowledge pupa → wisdom imago. Here wisdom is knowledge presented to the rest of existence for further digestion (and regurgitation).

Thread with much discussion and linkage regarding so many proposed solutions to essentially the same, simple problem.

Easy inline aliasing.

P.S. Aliasing here refers to the concept, not necessarily the technical term–aliases, so as to prevent further retread in the “YAML ain’t… YAML cain’t…”

1 Like

And for serious, very well communicated.


1 Like

Thanks! It took some iterations to formulate the simplest (?) solution for this very fundamental issue that I ran smack into within two weeks of using Obsidian. Which is amazing and has transformed my work :heart:

It does seem strange though that this rather simple (?) vision keeps being articulated for the past two years, since at least May 2020 in the thread you posted, and already twice since I made this topic six weeks ago:
Aliases, Inflection and Auto-Updating
Automatically insert aliases into YAML frontmatter

It seems to be a problem of different vocabulary referring to the same process? Maybe we could compile a list and go meta! :slight_smile:



Still hoping it’s either my technical ignorance or a semantical situation…

This is a great proposed implementation from recent:

Have exchanged PM’s with different thread authors and OPs which seem to indicate the feature remains absent.

These are two of the more poignant early threads discussing the same feature:


Great links with great ideas! They all point in the same direction, though I must admit that they already go far beyond my simple (fundamental) issue.

Which is that I don’t want to get additional functionality, but to simply be able to use the already existing functionality of “unlinked mentions”, which I have completely abandoned by now.

I cannot rely on them AT ALL if I have not manually lemmatized words with at least 5, but up to over 12 aliases (x2 for case sensitivity).


Let’s say I have a note on [Systems] (maybe linked under [Systems Theory] and maybe containing [Ant Mounds] or [Decentralized Synergy]). I might add the aliases (x2 for case-sensitivity):

nouns/ adj./ adv. verbs
system systemize
systematization systemizes
systematizations systemized
systematic systematize
systematical systematizes
systematically systematized


This is already a lot, and even in this case it would be great not have to do this in advance, but be able to spontaneously “send” an alias to this note if I happen to think of it when working on another note, without having to switch back and forth.

For German, the adjective and verb have to be adjusted according to the subject of the sentence (AND usually multiplied with the temporal tense, but I can spare you in this case :slightly_smiling_face:) (and as always, x2 for case sensitivity)

adj./ adv. (systematic) verb (systematize)
systematisch (adjective stem) systematisieren (verb infintive)
systematische (fem.) systematisiere (1st pers. sing.)
systematischer (masc.) systematisierst (2nd pers. sing.)
systematisches (neutr.) systematisiert (3rd pers. sing)
systematischen (pl.) systematisieren (1st pers. pl.)
systematischere (comparative sing. fem.) systematisiert (2nd pers. pl.)
systematischerer (comp. sing. masc.) systematisieren (3rd pers. pl.)
systematischereres (comp. sing. neutr.)
systematischeren (comparative pl.)
systematischste (superlative sing.)
systematischsten (superlative pl.)


Additionally, composite words can be and frequently are used like “systemimmanent” or “systemdestabilisierend” (system destabilizing) or “Denksystem” (thought system).

These ALSO need to be lemmatized or they disappear into the vault and have to be specifically searched for, loosing any chance of emergent ideas. :sob:

1 Like

Ideas for solutions:

  1. (bad)
    Having “unlinked mentions” somehow use lemmatization would clearly be ridiculously huge and complicated and unnecessary

  2. (best, but seemingly a unicorn) :rainbow:
    Optional fuzzy aliases so that alias: &{s}ystem& would magically solve everything (impossible in YAML)

  3. (please maybe)
    The suggestion in OP. This is such a tiny fraction… just to designate something as an alias when I run into it without having to leave the current note.

1 Like


Firstly, I’m definitely learning German (modularity in composite word crafting and word use–think of all the wonderful neologisms)!

Secondly, I’m incorporating lemmatize in to my personal knowledge management framework (granularity in the disambiguation of terms)!!!

And I think conceptually, it nicely frames the current dialogue.

In the service of the meta and of simplification: how can we better define and frame this issue that it may get traction and resolution?

We recognize there is a fundamental issue and that there is an essential direction pointing towards a solution. And it seems Obsidian natively has the capacity to resolve it, yet for reasons (jargon, language, semantics, tribalism, diversity of Developer & Userbase: technical skills, backgrounds, use cases, etc.) the issue remains unresolved…

That is, either the solution exists and we just don’t know it or this isn’t a problem because of essential limitations in either the tool or its intended Use/Userbase.

Quoth the gobble:

1 Like

Just pondering our original discussion through the lens of our new most favoritest plugin Push content to link from the creative genius of @lizard_heart!

@lizard_heart’s as-yet unnamed plugin, “The Inline-Disambiguation-anator”!

This syntax, from @syncretizm: [[target|>>alias]]>>{content} seems to provide some functional lemmatization? It creates a file called “target” with an inline aliased link called “alias” and YAML including the correct frontmatter aliasing and pushes or prepends/appends {content} as “any content” (including links, headings, etc.) to the body of the created or existing note, respectively.


alias: alias,

I think what’s so amazing, and seemingly unique about this plugin, is that it allows for Obsidian flavored aliasing in both the link AND the YAML, inline (woot!), and sans friction!

Just cross-posting here to pick up any watchers from this topic.

1 Like

Don’t forget to support the creator at Henry Gustafson for his great work

You can create an aliases field in the front matter of your new my-awesome-blog-post where you can add previous paths within the TXD tool Apk which very famous for Alias creation.

I am working on publishing and review of Obsidian plugin Link with alias which supports fast and handy creation of links together with their aliases in the front matter of the target note. I was already using that plugin for about 1 month while building my personal knowledge base with thousands of links. It already saved me a lot of time. I believe it can help you too.

1 Like