Good catch, this is just a bug I need to fix.
This is more easily controlled in stylesheet. Right now the built in stylesheet scaling everything small and then only scaling filter-match() back to normal size, but you can also use filter-match-ancestor() to scale match ancestors. Probably that should be done, but I just haven’t experimented with that possibility yet.
Yes, Bike doesn’t support discontiguous selections. It might someday, but probably not in 2.0 release. My solution for manipulating the matches is if you click on the match count in the filter bar you’ll get a popup … EXCEPT those actions are not actually implemented yet, but that’s the plan.
Maybe if you could break out a new topic with some suggested obvious searches that would be a good starting point. Along with any ideas you have for bringing simplicity to Bike searches. I think Bike’s outline path syntax is here to stay as powerful, but complex. But if there are things I can make easier I will try.
If you “shorthand” you mean predefined named searches, I think that might work. But I don’t think a new simpler search language would be simplifying at the moment.
The best way to limit that complexity that I can think of is saved (and maybe predefined) searches. So you only need to compose the search once, and then can reuse.
Not sure, but maybe this is a simpler way for task with highlighted text?
//task/run::@highlight
No! I appreciate the feedback, thanks for taking a look and thinking about how it all should fit together.