How do I get a cursor on every line in vscode
Visual Studio-CodeVisual Studio-Code Problem Overview
I'm trying to use the multi cursor functionality of vscode on a large(ish) file. the file is too large to select every line individually with ctrl-alt-up or down. In sublime-text I would select everything and push ctrl-shift-l. Is there a similar thing in vscode. I've tried using a regex search for ^, but that gives me an error stating "Expression matches everything".
Visual Studio-Code Solutions
Solution 1 - Visual Studio-Code
The command Selection / Add Cursors to Line Ends alt
shift
i
will put a cursor on every line in the current selection. (For mac use opt
shift
i
)
Tip: You can pull up the keyboard shortcut reference sheet with ctrlk,ctrls (as in, those two keyboard combos in sequence). (For mac use cmdk,cmds)
Solution 2 - Visual Studio-Code
Hold Alt+Shift and select the block. Then press End or Right button. You get selected individual lines.
I use version VSCode 1.5.3 in Windows.
Solution 3 - Visual Studio-Code
Solution 4 - Visual Studio-Code
This feature is actually called split selection into lines
in many editors.
- Sublime Text uses the default keybinding, CTRLSHIFT L
- VSCode uses ALTSHIFTI
- For Atom you actually need to edit your keymap to something like this
'.platform-win32 .editor, .platform-linux .editor': 'ctrl-shift-L': 'editor:split-selections-into-lines'
Solution 5 - Visual Studio-Code
Real Lines vs Display Lines
First we have to understand the difference between Real Lines and Display Lines to completely understand the answer of the question.
When Word Wrap is enabled, each line of text that exceeds the width of the window will display as wrapped. As a result, a single line in the file may be represented by multiple lines on the display.
The easiest way to tell the difference between Real Lines and Display Lines is by looking at the line number in the left margin of the text editor. Lines that begin with a number correspond to the real lines, which may span one or more display lines. Each time a line is wrapped to fit inside the window, it begins without a line number.
Cursor At the Beginning of each Display Lines:
Cursor At the Beginning of each Real Lines:
Answer to the Question
Now that we know the difference between Display Lines and Real Lines, we can now properly answer the actual question.
Hold AltShift and select the text block.
Press Home to put cursor on the beginning of every Display Line.
Press End to put cursor on the end of every Display Line.
Press HomeHome (Home twice) to put cursor on the beginning of every Real Line.
Press EndEnd (End twice) to put cursor on the end of every Real Line.
Please understand that AltShiftI put cursor on the end of every Real Line.
Solution 6 - Visual Studio-Code
Sublime Commands.
Install the extension> [Sublime Commands] Adds commands from Sublime Text to VS Code: Transpose, Expand Selection to Line, Split into Lines, Join Lines.
(Don't forget to add the keybinding(s) from the extensions details page to your keybindings.json
)
Doesn't VS Code already have a "split into lines" command?
Yes, yes it does. However it differs from the one in Sublime.
In VS Code, when you split into lines your selection gets deselected and a cursor appears at the end of each line that was selected (except for the last line where the cursor appears at the end of the selection).
In Sublime, when you split into lines a cursor appears at the end of each line (with the same exception as in VS Code) and the selection is divided on each line and "given" to the same line.
Solution 7 - Visual Studio-Code
I have the same problem, i'm used to Alt + drag to do 'box selections' in visual studio but it does'n work in code.
It seems to be impossible for now to do it differently than by selecting every single line.
However plugins should be supported soon so we will likely see a plugin for this if not implemented directly by microsoft.
From visual studio uservoice forums: >We plan to offer plugin support for Visual Studio Code. Thank you for your interests and look for more details in our blog in the coming weeks. http://blogs.msdn.com/b/vscode. > >For the preview we are looking for exactly this type of feedback. Keep it coming. > >Sean McBreen – VS Code Team Member