Conversation
|
This gets rid of the filter entirely in the view now, right? I'm not sure that's something we'd want to just remove without giving some replacement action in its place, even if it's just an explicit button that opens the find widget |
|
I just realized that currently, tree find is limited - it can only highlight matches found in the input. However, similar to the filter widget, it can filter results based on what is found in the output. Highlighting matches in the output might be possible when #212077 is accomplished. Thus, by default, I think we should use |
|
I wonder about removing the filter box entirely, when the replacement doesn't support all the same features (negative patterns). Any plan to support that in the tree find widget? |
|
Thanks. |
|
Ok, sounds good. I'll bring back the filter and will go with the default tree find keybinding, |
|
I hope it works the same as |
|
It does not atm as mentioned on the issue. That is the ultimate goal though |

fixes #4338
Follow up work will be:
find.mov