Vscode: Persist user choice in Find options (case, whole word, regex) in the Find widget in editor

Created on 6 Sep 2016  路  10Comments  路  Source: microsoft/vscode

  • VSCode Version: 1.4.0
  • OS Version: Mac OS El Capitan 10.11.4

Steps to Reproduce:

  1. Open VS Code and some file
  2. Cmd+F to find something
  3. Check the box to enable case-sensitivity and regex searching
  4. Close VS Code
  5. Open VS Code and some file again
  6. Cmd+F to find something

Expected behavior: the boxes for case-sensitivity and regex searching are checked.

Actual behavior: the boxes for case-sensitivity and regex searching are unchecked.

I _always_ want to search with these options enabled. How can I persist this state across restarts?

*duplicate editor-find feature-request

Most helpful comment

That works for me. I will do the following:

  • anytime a find widget toggle is changed, I will persist it (last one wins)
  • when the workbench starts up, I will read the persisted values and start with those by default.

All 10 comments

@jrieken The Find options are persisted for text search across files after restarting VS Code but not for text search in a file

Let's track in #10344 we should add a configuration option where you could specify the default toggle states.

I'd prefer we persisted user choice (notepad++, sublime and Visual Studio do persist user choice) rather than set configuration option explicitly. This way text search inside a file and across files would be consistent too.

@ramya-rao-a I haven't noticed Visual Studio persisting the user choice. Same as we, they have a find widget for each editor (so if you open multiple editors side-by-side they each get their find widget). What would we persist if we have multiple find widgets that have different toggles?

@alexandrudima Last writer wins? Honestly that's an edge condition, any decision is fine.

That works for me. I will do the following:

  • anytime a find widget toggle is changed, I will persist it (last one wins)
  • when the workbench starts up, I will read the persisted values and start with those by default.

Any updates on this matter ?

Trying out vscode after hearing much hype lately, and this is my biggest issue in adopting it.

I use (cmd+d) multiple cursors a lot, and having to do cmd+f and toggling case-sensitive every time I open an editor is a pain in the rear-end.

Even if I could use cmd+alt+c (my hotkey for alfred snippets) it would still be annoying.

Still annoyed by this on a daily basis as well :)

Let's track the setting persistence in #6158

Was this page helpful?
0 / 5 - 0 ratings