[Feature Request] User can create search command with predefined condition

[jiamingz42]

Use Case

My vault contains personal and work-related notes. I place all work-related notes under the same folder or tag them with #work

When I am at work, I want to only search notes related to work. I can start each query with "#work" but it becomes very tedious.

If I am actively working on project-a, I may need to start each query with #work #project-a.

Solution

In the plugin's settings page, users can add a custom search command. Users can specify predefined conditions and other options (e.g. ignore normal path patterns).

For example, I will add a custom search command. Name it "work search". And set the predefined conditions to "#work". As for the options, we can narrow the search to a specific folder.

The plugins will register this command with Obsidian. Then the user can either access it through the command palette or assign a shortcut.

[tadashi-aikawa]

Hi, @jzhang-brex.

I agree with your use case and solution.

The plugins will register this command with Obsidian

I will try it as well as I can.

Users can specify predefined conditions and other options (e.g. ignore normal path patterns).

I will consider the predefined conditions (obviously), but I will not consider the options.

[tadashi-aikawa]

@jzhang-brex
I have released this feature in v6.0.0-beta4 🚀

If you use BRAT, please confirm whether it works as you expected. Of course, It would be great to have feedback or bug reports :)

[rapatel0]

Not sure if I'm doing something wrong

The hotkey command for a specific search works beautifly but the :p doesn't seem to be working with the recommended search

Config:
Custom command: Projects
Default input: #T/Projects
Command Prefix: :p
Priorities:

• Tag match
• Prefix name match
• Name match
• Header match
• Link match
• Last opened
• Last modified

Hotkey trigger (works perfectly)

Recommended search trigger (doesn't seem to be working)

[tadashi-aikawa]

Thank you for your report, @rapatel0 :)

That is a good point out. But unfortunately, the search using Command Prefix don't consider Default Input and Ignore prefix path patterns for now.

I'll consider them by modifying the UI of the dialog. Please wait for the next beta release 👍

[tadashi-aikawa]

@rapatel0
Released in v6.0.0-beta8 🚀

2022-08-11_20h41_38.mp4

[rapatel0]

Beautiful This is awesome

[rapatel0]

I assume that you're still working on it but. It's not clear how to indicate ignore prefixs. I used newlines to sepearte them but they don't seem to filter correctly,

Target folder: Areas/
(implemented by ignoring everything else)

Areas with (:a)

:a Not working

[tadashi-aikawa]

@rapatel0
As far as I saw your images, it seems that you didn't set / and Binary Files/ in "Ignore prefix path patterns.

[tadashi-aikawa]

Ah.. it is not easy to ignore /. So please wait to implement Includes prefix path patterns.

#78 (comment)

[tadashi-aikawa]

I have released v6.0.0-beta10 🚀

@rapatel0
The new beta version enables you to set Includes prefix path patterns. Please try it :)

[tadashi-aikawa]

Released in v6.0.0 🚀