Can you explain search steps? How they're activated, etc. It looks like they have been very customized for your setup.
Thanks! On Thursday, July 22, 2021 at 3:06:42 PM UTC-7 [email protected] wrote: > @Mark S; I particularly like the command palette > <https://souk21.github.io/TW-commandpalette/> plugin for searches. > > Please note it is not designed for Streams, but can be made to work quite > nicely with it because the search steps are highly configurable through > the $:/plugins/souk21/commandpalette/CommandPaletteSearchSteps tiddler. > Here's an example of what I use at work; you'll notice I give precedence to > title matches (they'll be at the top of the results) and use the > get-streams-root[] filter extensively. The command palette adds a > category (hint) in the search results which I find helpful. > > { > "steps": [ > {"filter": > "[!is[system]tag[todo]search:title:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]", > "hint": "todo (titles)", "caret": "42"}, > {"filter": > "[!is[system]tag[todo]search:text:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]!tag[done]]", > "hint": "todo (text)", "caret": "41"}, > {"filter": > "[!is[system]tag[Meeting]search:title:literal[]!sort[title]]", "hint": > "meetings (main)", "caret": "45"}, > {"filter": > "[!is[system]tag[Journal]search:title:literal[]!sort[title]first[2]]", > "hint": "meetings (titles)", "caret": "45"}, > {"filter": > "[!is[system]tag[Journal]search:text:literal[]get-stream-root[]!sort[title]]", > "hint": "meetings (text)", "caret": "44"}, > {"filter": "[!is[system]search:title:literal[]get-stream-root[]]", > "hint": "others (titles)", "caret": "33"}, > {"filter": "[!is[system]search:text:literal[]get-stream-root[]]", > "hint": "others (text)", "caret": "32"}, > {"filter": > "[!is[system]tag[todo]search:literal[]get-stream-root[]!tag[Journal]!tag[Meeting]tag[done]]", > "hint": "completed", "caret": "42"}, > {"filter": "[!is[system]search::literal[]get-stream-root[]]", > "hint": "all", "caret": "28"} > ] > } > > I have configured the command palette to fire on a single key shortcut (/). > Whilst TiddlyWiki offers keyboard shortcuts, they fire everywhere out of > the box, even within text boxes (not ideal for single key shortcuts!), so > my setup relies on the mousetrap > <https://welford.github.io/#%24%3A%2Fplugins%2Fwelford%2Ftwmousetrap> > plugin: hitting / in a text box does not fire the command palette. I am > working on a tweak that will have a richer set of search steps > configuration, so that I can invoke the command palette to search for tasks > (I use projectify <https://projectify.wiki/>) using shift+/ and to search > in other tiddlers when I hit /. > > In other parts of the UI, I have essentially inserted the subfilter " > get-stream-root[]" everywhere, so that the recent tab, the sidebar > searches, etc only show root tiddlers in the results. > > I think one of the other members in the community here configured the > names of node tiddlers to be prefixed with $:/ which makes them system > tiddlers, which effectively hides them from most searches... another option > worth considering and simpler to setup. > > On Thu, 22 Jul 2021 at 15:02, Saq Imtiaz <[email protected]> wrote: > >> >> Is there a search tool or plugin that works with streams? Streams is neat >>> to take notes with, but searching is problematic since the default search >>> shows you only the titles. Possibly someone has already written a custom >>> search? >>> >> >> @Mark S: >> >> I don't think there is a good generalized solution for this yet. Needs >> vary depending on people's workflow and title naming setup within Streams. >> I have posted a search customization for a specific users workflow at one >> point to show what customizations for search might look like. >> >> If you just want search results to show the root tiddler title as opposed >> to the titles of individual nodes, the attached file adds a tab to the >> search results to do that. If I remember correctly, title matches are >> returned unchanged whereas text matches only return the root tiddler. >> >> The missing piece is of course that once you find and open the root >> tiddler, it can be tricky finding the text you searched for within that >> stream. >> >> -- >> > You received this message because you are subscribed to a topic in the >> Google Groups "TiddlyWiki" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/tiddlywiki/-xTFWPwzq6g/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> > To view this discussion on the web visit >> https://groups.google.com/d/msgid/tiddlywiki/1ab33144-87d6-4d95-8c77-e05565891025n%40googlegroups.com >> >> <https://groups.google.com/d/msgid/tiddlywiki/1ab33144-87d6-4d95-8c77-e05565891025n%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/89f9bd2b-b523-43a1-a868-6f76495da4fdn%40googlegroups.com.
