Visual Studio Code - NEW FEATURES: 4 Editor Improvements (Find/Replace, Cursor Blinking, Select Current Line, & Scroll Viewport)
The 0.10.5 December release features a plethora of improvements, including...
Editor Improvement #1 - Find/Replace improvements
In regex mode:
- Can now search for
^
,$
or^$
thanks to a community contribution. - Can now replace with
\n
or\t
.
Keyboard shortcuts:
- New Find settings commands: toggle case-sensitive (Alt+C), toggle regex (Alt+R) and toggle whole word (Alt+W)
- Ctrl+F puts focus in the Find input field.
- Ctrl+H puts focus in the Replace input field.
- When focus is in the Find widget input fields, Ctrl+Down put focus in the editor.
Editor Improvement #2 - Cursor Blinking Options
New setting to configure cursor blinking: editor.cursorBlinking
with values blink
, visible
and hidden
thanks to community contribution.
Editor Improvement #3 - Select Current Line Command
New select current line command (Ctrl+I) thanks to a community contribution.
Editor Improvement #4 - Scroll Viewport Commands
Thanks to a community contribution, VS Code has improved editor scroll support:
- Scroll by one line up (Ctrl+Up) / down (Ctrl+Down)
- Scroll by one page up (Ctrl+PageUp) / down (Ctrl+PageDown)
Special thanks to the community for contributing most all these improvements! You can click the community contribution links above to go to the GitHub pull requests and check out who did what!
Check out all the new features and update to Visual Studio Code v0.10.5:
https://code.visualstudio.com/updates
Have a good bye!
- Ninja Ed
Comments
Anonymous
January 30, 2016
Computers Today (part 1 of 6) blogs.msdn.com/.../computers-today.aspx CS SPOTLIGHT: Girls in computer programming... why it matters!!! blogs.msdn.com/.../cs-spotlight-girls-in-computer-programming-why-it-matters.aspxAnonymous
February 22, 2016
How do we automatically put the currently selected text into the Find input field? Without that, the Ctrl+H is broken because we always need to go back into the Find input field to key in some text for replacement.Anonymous
February 27, 2016
WS, Good question. Please post as an issue on GitHub to get the proper attention: github.com/.../issues Thank you!