Thread by @RobertHaisfield

Assuming you're not using aliases, a plain text search in @obsdmd for "[[page]]" within quotations pulls up the backlinks for that page. Searching for ".png" will pull up all of your pngs. There's a lot of flexibility that comes from searching strings when everything is in markup

Here I have an embedded query to find all my notes directly dealing with DSLs (domain-specific languages). I get this by searching for file names that have DSL in them. In Roam I might have had [[A [[DSL]] speeds up the author and gives them the ability to write from anywhere]]

Here I'm trying out using namespacing in a @dendronhq style. I have an embedded search looking for pages that have Clojure and function in the title. It's not officially supported in Obsidian, but with searches embedded on pages, I'm able to do it quite flexibly

Obsidian lets you use #nested/tags, but what if you have an item that exists within multiple hierarchies? For example, I have #people/spark-wave and I have #spark-wave/GuidedTrack. This search will capture both, allowing nested tags to exist inside and outside of hierarchies!

The above tweet lets you break the way Obsidian normally functions in a good way! I'm amazed at how much you can do to define your own systems with "string" search rather than just backlink querying. Then embedding those searches on pages makes the searches themselves searchable!

When you think about it, the backlinks to [[page]] being a search for "[[page]]" essentially represents a smart default for what is related to that page within your vault. I want to break those defaults and further define what counts as a "backlink" via a well-formed search term!

I'll note - this is implicitly what I do with my [[open questions]]. Here's an example from @RoamResearch: the top level bullet has a question, and then I translate that question into a query of my database. I'm doing the same thing now in Obsidian with embedded queries.

What I like about that approach is it allows me to pull related content without having to remember to reference the specific question - I'm just talking about stuff related to the question and the search "knows." It allows me to say "when I say this, this is what I really mean."

Not every search goes on a page. Sometimes I just use the search bar if I'm trying to find something real quick. However, any time that I embed a query on a page, that reifies it into an auto-updating part of my knowledge management system.

This is making me wish I could define variables and then search for those, and then those variables could be either manually specified or dynamically set by the results of an advanced search.

https://twitter.com/round/status/1198367899758387200?s=20