Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Search: remember string when accidentally invoking history navigation (up/down arrow) #54018

Closed
borekb opened this issue Jul 11, 2018 · 5 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug search Search widget and operation issues verified Verification succeeded
Milestone

Comments

@borekb
Copy link

borekb commented Jul 11, 2018

Version 1.25 (June 2018) changed defaults for history navigation to plain up/down arrows where this previously moved between fields (implemented in #12645). I like the change itself but often press up/down arrow accidentally as my muscle memory is used to navigating between fields with that.

The problem is that up/down arrows now navigate history, losing what I just typed. Imagine I carefully write some regular expression in the search box, want to limit it to *.md files so I press the down arrow.. ooops, my regex is gone.

The proposed change here is to remember what I just typed into the field. For example, I write my regex, press down, realize that this is a history navigation command (which itself is debatable; shouldn't history navigation be triggered by Up only, like in terminal?) so I press the opposite arrow and my regex is back.

Thanks for considering this.

@vscodebot
Copy link

vscodebot bot commented Jul 11, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@vscodebot vscodebot bot added editor editor-find Editor find operations labels Jul 11, 2018
@Tyriar Tyriar added search Search widget and operation issues and removed editor editor-find Editor find operations labels Jul 12, 2018
@roblourens
Copy link
Member

roblourens commented Jul 12, 2018

The proposed change here is to remember what I just typed into the field.

This is supposed to work and it does work for me. In which field are you testing this, and on what platform?

@roblourens roblourens added the info-needed Issue requires more information from poster label Jul 12, 2018
@sandy081
Copy link
Member

I see.. I think I got the issue. I think it happens when you have the history when you navigate to next.

@sandy081 sandy081 added bug Issue identified by VS Code Team member as probable bug and removed info-needed Issue requires more information from poster labels Jul 13, 2018
@sandy081 sandy081 added this to the July 2018 milestone Jul 13, 2018
@borekb
Copy link
Author

borekb commented Jul 15, 2018

Correct, I already have some history so pressing down arrow replaces my search string with an item from the history, with no way to get my manually typed text back (all this is before I pressed Enter for search so my search string has not been added to the history yet). @sandy081, thanks for looking into it!

@sandy081
Copy link
Member

To Verify

  • Search for value 1
  • Search for value 2
  • Search for value 3
  • Type Up Arrow to reach 2
  • Clear the input and type 4
  • Type Down Arrow
  • Verify that value is not changed
  • Type Up Arrow
  • Verify that value is changed to 3
  • Type Down Arrow
  • Verify that value is changed to 4

@mjbvz mjbvz added the verified Verification succeeded label Aug 2, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators Aug 30, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug search Search widget and operation issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants