@ Symbol Linking

approved

by Evan Bonsignori

Link to notes with any symbol (e.g. `@`). Can map symbols to link to a specific directory or to create files in directories using templates.

93 stars15,225 downloadsUpdated 6mo agoMIT
View on GitHub

@ Symbol Linking

Gif demo of using the @ symbol to link to a name in Persons/

Adds the ability to link using any symbol (e.g. @) in Obsidian. Can limit linking to specific folders, like People/, or map specific characters to open specific folders, like $ to open References/ and @ to open People/ for more information see release 2.0 notes.

Supports aliases (nicknames for a file) that you can set in the properties/metadata of a note via the alias or aliases field.

Settings

  • Limit symbol links to only source links from specific directories, like your People/ directory.
  • Create a new note from a template in a specified directory if no symbol link is found.
    • As of v2+ you can specify symbols to create notes from specific templates in given directories.
  • Turn on compatibility mode to enable symbol linking when plugins that show suggestions like the Tasks plugin are enabled.
  • Optionally include the linking symbol in the final link text, e.g. [@evan](./evan.md) as opposed to [evan](./evan.md)

Inferred settings

  • Uses the link type specified by your Obsidian "Files & Links" -> "Use [[Wikilinks]]" setting.
  • Uses the link format specified by your Obsidian "Files & Links" -> "New link format" setting.

Hotkeys

Supports up, down, enter, and escape keys for navigating the link search popup.

Installing

Search "@ symbol linking" via the built-in community plugin browser in Obsidian.

Contributing

Please open an issue with any suggestions or bug reports.

See developer docs if you'd like to open a PR.

Acknowledgements

The Obsidian team for creating a wonderful product :purple_heart:

The implementation borrows from:

For plugin developers

Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.