Property-based note navigation: within scope? #971
Replies: 2 comments
|
that sounds good, would love to see the PR
but we already do tons of stuff and the whole plugin is basically organize around pickers lol, so it is very welcome and I am not sure is the proposal inspired by #928 if not you can go have a look
just a clarifying question: by this do you mean your implementation don't depend on the cache module? that sounds like a slow operation if only rg does this, just a thought, would love to see the PR and discuss more |
|
Right, it didn't. Switched it to read from the cache module instead, falling back to the full scan when it's disabled. Added a test confirming zero filesystem calls on the cache path. One disclosure: this was vibe-coded (Claude Code did the implementation, I reviewed and directed it). Flagging that up front in case it changes how closely you want to look at the diff. PR's up: #978 |
Uh oh!
There was an error while loading. Please reload this page.
I use frontmatter properties to organise notes and would like to navigate them from Neovim: choose a property, choose a value, then open a matching note.
For example, with notes containing:
Running
:Obsidian propertieswould let me selectstatus, thenactive, then pick a matching note to open. If I already know what I’m looking for,:Obsidian properties status activewould open the matching-note picker directly.I have a local implementation of
:Obsidian properties [KEY] [VALUE]. With no arguments it opens that three-stage picker; supplying a key or key/value skips the corresponding stages. It uses obsidian.nvim’s existing note search, frontmatter metadata and picker interface, with no dependency on a separate query plugin or a particular note schema.Before opening a PR, I’d like to check whether this fits obsidian.nvim’s scope as a companion to Obsidian. It uses existing frontmatter without introducing new syntax, but the picker itself is a Neovim-specific interface.
Would this be welcome upstream?
All reactions