'Searching for:' not showing actual search string
See original GitHub issueIs this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT
What happened:
When searching with <kbd>/</kbd>, VSCode status bar shows --SEARCH IN PROGRESS-- Searching for:
but doesn’t show string currently being searched.
What did you expect to happen: Bottom bars shows string entered for search.
How to reproduce it (as minimally and precisely as possible):
Environment:
- Extension (VsCodeVim) version: Sunny Seattle
- VSCode version: 1.19.1
- OS version: Ubuntu 17.10
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
How to search in Outlook - Microsoft Support
To search for an exact string, you must use quotation marks. Items sent from bobby moore. Note the use of double quotes so...
Read more >Searching for a string in a file is not working in Python
I am currently testing with Sublime for Windows editor - which outputs a 'NUL' character between each "real" character which is very odd....
Read more >2a. Search Strategies - How to Do Research: A Step-By-Step ...
Search Strings. Are you finding too much or not enough information? Try using boolean operators and truncation symbols, or use alternative, ...
Read more >Refine web searches - Google Search Help
Refine web searches ... You can use symbols or words in your search to make your search results more precise. Google Search usually...
Read more >FIND—Find a Search String - IBM
You can use FIND with the EXCLUDE and CHANGE commands to find a search string, change it, and then exclude the line that...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It doesn’t matter what vscode you are running. I shipped out a new version last night so that’s probably why you see it.
I’d prefer to keep
-- NORMAL --
as that’s an indication that the vim extension is loaded, and also prevents any vim beginner-eque questions about “what mode am i in?”Yeah, agreed.
Not do-able. there’s an existing issue somewhere in our issue list about this, but it’s reliant on VSCode APIs.
Glad to see your fast integration! I saw the change in the code-insiders now.
How about simplify the display further and make it more ‘vim’
-- INSERT --
instead of-- INSERT MODE --