Sometimes navigating the Tag pane to build searches using the convenient Ctrl click technique becomes cumbersome.
Proposed solution
If you had the various tags of immediate interest open in a note or multiple notes and could Ctrl click them in sequence, building a search like in the Tag pane, life would be a little easier.
Current workaround (optional)
Nested tags could make this easier. Or potentially, if tag folders existed, this could be somewhat easier. See link below.
I agree with this approach. That way a note would be specifically made for searching a specific topic. I would use this in the example of Leetcode Problems.
Leetcode Example
I can have a section for difficulty (easy, medium, hard), algorithmic paradigm, data structure, status (solved, unsolved), etc. Then by ctrl-clicking it would be quick to form a search and find my desired problem.
This would also solve my issue with nested tags. By having each of these leetcode tags nested under the tag leetcode, I have a lot of clutter on the screen given that a problem could have the tags: leetcode/binary-search leetcode/array leetcode/hash-table leetcode/solved leetcode/divide-and-conquer leetcode/sorting… Or even worse if I wanted to further categorise the tags (for example according to the categories listed in the above example).
Further Examples
Some further examples that also come to mind are: recipes, movies, places…
I really like the idea of being able to Ctrl/Cmd-click tags directly within a note to build a search. It would save a lot of time compared to navigating through the Tag pane, especially when working with multiple tags in different contexts. It just feels like a natural feature to have, and would definitely help with smoother searches, especially for notes that span various categories.
When using Require #Tag in search, a tag get appended to the search query. This fulfills this feature request, albeit via the context menu, not a hotkey. But this may even be preferable because it means that it also works on mobile. If a hotkey is desired, it may be best to direct such a request to the plugin’s repo.