vscode
vscode copied to clipboard
microsoft
Virtual Space is not implemented.
https://blogs.msdn.microsoft.com/zainnab/2010/02/28/understanding-virtual-space/
This is a much needed productivity option that has been available in Visual Studio and other editors for many years.
See also the column select issue that requires it: https://github.com/Microsoft/vscode/issues/5402
Addition from @hediet:
This is (still) the current behavior of VS Code. Only text that exists in the text buffer is selected:
However, the column selection mode should support rectangular selection like this (adding whitespace on demand):
This would fix #5940 (which is just about copy&pasting such blocks) and #115559.
I'm not sure we need a new issue for this if it's just part of #5402. Looks like there's lots of history there already.
Completely fixing #5402 requires this, but this can be implemented without the changes to column selection.
I see. Virtual Space - https://blogs.msdn.microsoft.com/zainnab/2010/02/28/understanding-virtual-space/
+1 for this feature. Virtual space is a must-have for me. I really like the editor otherwise, but until this is in I'll have to keep using Visual Studio. I hope it makes it out of the Backlog soon!
@itadapter: I don't think you're missing something. The feature isn't there. Looking at related threads about column select features, it appears the stance is that column select doesn't require virtual space. To my knowledge, @alexandrudima hasn't responded directly to anyone about virt space, only to questions about column select.
Virtual space isn't available in Atom or Sublime either. I always thought BRIEF was a common background for programmers looking for a non-IDE experience, but apparently not if all 3 of the modern alternatives do not implement the feature.
These are common things I do in my other editor. If there's a way to do them in VSCode that would be great. Seems like they need virtual space
If you're not a fan of aligning tables many coding standard align comments
Those are maybe minor examples but I find that I'm missing them quite a bit moving to vscode. Here's another example
vs VScode
This isn't just about comments, it's about being used to column select with cursors in virtual space. In my editor at least which pre-dates multiple cursors (though it has them now) the main cursor can't go into virtual space (well actually that's configurable), but once column selection is started then it can go through virtual space.
Executing the "Go to Line..." command when specifying a line number past the end of the file (and/or a column number past the end of the line) should also place the cursor into virtual space.
Would it be possible for someone on the dev team to comment on whether the virtual space feature is even a good fit for the editor internals? I'm wondering if it's something I should be hopeful about being added at some point, or if it's perhaps unlikely due to large refactoring cost vs minimal benefit (small number of users who really want it).
+1. There are a few things that prevent me from switching to VS Code, but this is a big one.
This is a deal killer! Here I go again opening notepad++ becasue an editor does not have a feature that is part of my daily workflow!
Seriously guys on the Visual code team, communicate to each other in your company because that's one of the most powerful features and it was there for more than 18 freaking years in Visual Studio.
https://blogs.msdn.microsoft.com/zainnab/2010/02/28/understanding-virtual-space/
That's why we use an editor instead of Word (fixed font size and virtual space) when it comes to write code fast.
@jchatel we have to keep in mind that this product is both free and good when asking for new features. I wouldn't call virtual space a particularly powerful feature. I feel like its absence is more of a high barrier to adoption among many of us who formed our editing technique with it.
Also, I use proportional fonts AND virtual space in VS. They are definitely not mutually exclusive.
I'm encouraged that the issue isn't closed. Perhaps the team is committed to adding the feature but is facing some refactoring costs that need to get planned for. I can imagine that adding virtual space after the fact might break a lot of code that can otherwise assume the cursor is always on a physical character.
On the other hand, I've seen the phrase "cursor floating in air" used by a VS Code developer somewhat pejoratively. This discourages me and makes me wonder if the team instead might be considering closing the editor to those who work that way.
Any comment from the dev team on which way this is heading would be pure gold to many of us.
There's multiple issues conflated here.
For example in my editor of choice I have virtual space off. But, my editor (like Visual Studio but unlike VSCode) has a column select mode. The column can go through virtual space and is an extremely powerful feature that I use many times a day and end up being frustrated having to tediously manually edit when in VSCode. (see gifs above).
Column editing solves a host of issues that multiple cursors do not (and vice-versa). Both features are important and powerful but at the moment it seems like column editing can not be added without support for virtual space.
Column select discussion is here (I think there are others too): https://github.com/Microsoft/vscode/issues/5402
This thread is about virtual space only, described very well by the link jchatel provided: https://blogs.msdn.microsoft.com/zainnab/2010/02/28/understanding-virtual-space/
Virtual space may be a dependency of fixing 5402 to most people's satisfaction, but they are separate. No need to conflate the two here.
The conflation comes from your previous comment. You basically said virtual space is mostly useless
I wouldn't call virtual space a particularly powerful feature. I feel like its absence is more of a high barrier to adoption among many of us who formed our editing technique with it.
But it's not useless at all. It's required for column editing since you have to be able to move through virtual space to use columns as columns. Column editing is immensely powerful. So please don't go dismissing virtual space as useless.
Conflation is taking two separable issues and muddling them together as though they were the same, not from a subjective judgement about how important one of the two issues is. Some of us who want virtual space aren't bothered by the current column select implementation at all.
Virtual space is not useless. There are many of us in this thread who are eagerly anticipating it's possible implementation, and who can't use VS Code without it.
I agree. Not being able to easily get rid of columns of virtual space is a huge deal breaker for me. Was hoping to start using VS Code for work, but i'm going to have to go back to Notepad++.
This is an important feature for the editor. I always use it. I would like it implemented.
To add to the chorus... I do a fair amount of editing like greggman's images above show. This is a deal breaker for me as well. No moving my cursor, let me do it and give me a convenient toggle.
Please! :)
I can't believe this otherwise amazing editor hasn't virtual space. I use it very day, and I have to open a separate text editor (PsPad) just for that.
Thanks for your work on Visual Studio Code but I have to agree with the others. Virtual space should be a must have for any code editor. I can't understand why would anyone not want it enabled. If I change the line and then return to the same line the cursor position should remain at the same position that it was. Without virtual space it's going to be in a random position depending on how long are the lines I traversed. I call that behaviour a bug, to be honest.
Everybody could just subscribe to the thread and wait until the contributors have anything valueable to say instead of constantly posting the same "arguments" here. Will anybody lock the thread until then?
@paulsmirnov That depends on why it hasn't been implemented yet. If it's because there hasn't been enough interest expressed here yet, then additional voices may be helpful. Since we haven't had any feedback here from the VS team in almost 2 years, it's hard to know.
I agree with @gregmarr that more voices = proof of interest = hopefully the team might consider it a priority.
I do wish the comments were a little less entitled feeling. Stuff like "this is deal breaker", like there is no deal. It's a free project. No one owes us anything.
Still hopeful the team will see the utility and decide to add support.
as for @m6502 , I am unable to repo the issue you describe. I made a line with 2 tabs followed by 2 spaces followed by code. Above and below that are lines with 3 tabs. No mater where I put my cursor in the line with spaces going up and down always returns to the same place.
Maybe a gif showing the issue and another showing no issue in some other editor would be helpful to see the issue?
Locking the thread might be interpreted by MS as lost interest in the feature and it may never get considered.
From: Paul Smirnov [email protected] Sent: Tuesday, 23 October 2018 6:15 AM To: Microsoft/vscode Cc: tkimovski; Comment Subject: Re: [Microsoft/vscode] Virtual Space is not implemented. (#13960)
Everybody could just subscribe to the thread and wait until the contributors have anything valueable to say instead of constantly posting the same "arguments" here. Will anybody lock the thread until then?
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode%2Fissues%2F13960%23issuecomment-431942676&data=02%7C01%7C%7C7364612a6cfb4b50f70a08d63852c62b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636758325486729722&sdata=%2FFoCmydGTtl85Ot0T87mxFOeuVh9VYQfn%2B8IApWsxec%3D&reserved=0, or mute the threadhttps://nam02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FANLVXcjyAC8FhMT_BiXT7mmtvCZqqOxqks5unhljgaJpZM4KaQAK&data=02%7C01%7C%7C7364612a6cfb4b50f70a08d63852c62b%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C636758325486729722&sdata=iSAcpT1iN6%2BhBM%2BpGodOQBp6klgkV5IXFBxtrNysdJ8%3D&reserved=0.