Search editor - Remember recent filter regexes

[chavlji]

Search inside editor is an awesome feature!

It would, however, be much more useful with that small tweaks:

• remember state (show/hidden) of Search details panel
• remember the last content of fields files to include and files to exclude
• remember recent file filters

Sublime does all of this very good and I've used it all the time:

[gjsjohnmurray]

Are you aware that cursor-up in these fields can recall previous entries?

[roblourens]

You can navigate history with the arrow keys like @gjsjohnmurray points out

[chavlji]

Nope, it doesn't work in these fields. I'm using the latest insider version.

Besides don't just close it. Even if it would work it would only answer my 3rd point. What about the 1st and 2nd?

[roblourens]

1. The state is remembered per workspace. Can you give some more details about where you are not seeing that work?
2. The arrow keys
3. Can you explain what you mean by file filters?

[chavlji]

Sure. Thanks for reopening!

I press cmd+shift+f and set the search like this:

I close the search tab.
Press cmd+shift+fagain and all fields are reset:

How it should be
imo when I reopen it, it should look like where I've left it:

• search filed filled with previous string ('target')
• search details opened
• files to include/exclude filled with previous filters:

It seems like a minor issue but It's very cumbersome when you work on a large new project and you have to search a lot...

* Up/down arrows do work - thanks for the hint. But it would be nice if I wouldn't have to focus fields all the time and pressing arrow keys to restore the state...

[JacksonKearl]

Please try out "search.searchEditor.experimental.reusePriorSearchConfiguration": true in Insiders and let me know what you think.

Its a hidden setting, you'll have to enter it into settings.json manually.

[chavlji]

What do I think? I love it!!!

Thank you @JacksonKearl !

Also... imo it should be the default behavior. More times the user would want app to remember state than not.

[JacksonKearl]

Discussing options for the future in #89353