Looking at Atom and VS Code
-
The VSCode settings are all in the settings section. Depending on the extension, some don't have a gui part, so you just modify it in the settings.json file.
As for the line movement, I've never had it jump to the end of the line. Arrowing up and down stays in place unless there is a break where it can't and then it will jump to that position.
-
As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.
-
@stacksofplates said in Looking at Atom and VS Code:
Arrowing up and down stays in place unless there is a break where it can't and then it will jump to that position.
That's the part that I don't want. Almost all code editors has a setting for this. There is just no standardized name for it AFAIK.
-
@stacksofplates said in Looking at Atom and VS Code:
As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.
Great thanks. Too bad it's not just a simple setting.
-
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
Arrowing up and down stays in place unless there is a break where it can't and then it will jump to that position.
That's the part that I don't want. Almost all code editors has a setting for this.
Can you give an example of one that does? Idk how that's possible if the line above doesn't have an element in that column how it could stay in that column?
-
@stacksofplates said in Looking at Atom and VS Code:
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
Arrowing up and down stays in place unless there is a break where it can't and then it will jump to that position.
That's the part that I don't want. Almost all code editors has a setting for this.
Can you give an example of one that does? Idk how that's possible if the line above doesn't have an element in that column how it could stay in that column?
-
@stacksofplates said in Looking at Atom and VS Code:
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
Arrowing up and down stays in place unless there is a break where it can't and then it will jump to that position.
That's the part that I don't want. Almost all code editors has a setting for this.
Can you give an example of one that does? Idk how that's possible if the line above doesn't have an element in that column how it could stay in that column?
I found this when searching for what it's called in different editors.
It's called "virtual space" in VS (Visual Studio).
https://github.com/microsoft/vscode/issues/13960 -
Interesting. Not something I've ever even thought of. I pretty much enable vim mode on everything I use so I've never thought to try something like that.
-
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.
Great thanks. Too bad it's not just a simple setting.
Having the settings in JSON like that is nice because it's easy to back up. There's an extension that syncas all of your extensions and settings to a gist in GitHub.
I still use VSCode a good bit but most of my stuff is done in JetBrains tools now.
-
@stacksofplates said in Looking at Atom and VS Code:
Interesting. Not something I've ever even thought of. I pretty much enable vim mode on everything I use so I've never thought to try something like that.
It's one of those things that's a deal breaker if you are used to it.
It's nothing new, it's been around forever.In vim it's the virtualedit=all setting. It's called "cursor beyond EOL" in some editors. In some editors it was the default mode.
Had a look and JetBrains has it too. Under "Virtual Space" there are a couple of settings.
It sure seems like VS Code and Atom are not as versatile as I thought, since to me this is a pretty basic feature.
-
@stacksofplates said in Looking at Atom and VS Code:
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.
Great thanks. Too bad it's not just a simple setting.
Having the settings in JSON like that is nice because it's easy to back up. There's an extension that syncas all of your extensions and settings to a gist in GitHub.
I still use VSCode a good bit but most of my stuff is done in JetBrains tools now.
Had a look at that feature in the JetBrains editors too and they have a simple setting to select the behavior you want.
-
@Pete-S said in Looking at Atom and VS Code:
It sure seems like VS Code and Atom are not as versatile as I thought, since to me this is a pretty basic feature
I'm assuming it's an underlying limitation of Electron since both are built on that.
-
Saying they aren't versatile because of that one feature seems a little disingenuous. I'm sure if it was a simple thing to add or more people wanted it, it would be there.
-
@stacksofplates said in Looking at Atom and VS Code:
Saying they aren't versatile because of that one feature seems a little disingenuous. I'm sure if it was a simple thing to add or more people wanted it, it would be there.
I don't think it's disingenuous at all, not if the primary purpose is an editor for developers.
You'd expect a good deal of customization for something like that. That is what versatility is.It's really a common basic feature. Just to name a few - VS has it, vim has it, JetBrain have it, Notepad++ has it, CodeLite has it etc. If people didn't ask for it, nobody would have it.
But for sure, VS Code and Atom may be versatile in other areas - besides the actual code editing.
-
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
Saying they aren't versatile because of that one feature seems a little disingenuous. I'm sure if it was a simple thing to add or more people wanted it, it would be there.
I don't think it's disingenuous at all, not if the primary purpose is an editor for developers.
You'd expect a good deal of customization for something like that. That is what versatility is.It's really a common basic feature. Just to name a few - VS has it, vim has it, JetBrain have it, Notepad++ has it, CodeLite has it etc. If people didn't ask for it, nobody would have it.
But for sure, VS Code and Atom may be versatile in other areas - besides the actual code editing.
Yes it's still disengenuous. I know quite a few people that use VSCode as their full time IDE/editor and this is literally the first time I've heard this complaint.
Yes versatile in other areas like having a functioning debugger, live share, containerizing the whole dev environment, really decent git integration, decent built in terminal, etc. All things developers care about.
The tools still have more than "a good deal of customization".
This is like saying a mercedes isn't a good car because it doesn't have a heated steering wheel.
-
snaps back to the correct place in Vim mode :man_shrugging:
-
@stacksofplates said in Looking at Atom and VS Code:
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.
Great thanks. Too bad it's not just a simple setting.
Having the settings in JSON like that is nice because it's easy to back up. There's an extension that syncas all of your extensions and settings to a gist in GitHub.
I still use VSCode a good bit but most of my stuff is done in JetBrains tools now.
Sync is built in to VSCode for a bit now.
-
@stacksofplates said in Looking at Atom and VS Code:
snaps back to the correct place in Vim mode :man_shrugging:
It does by default.
I've never come across a need for virtual space. If I don't have anything written on a line, I wouldn't need a line comment there?
I've always used comment blocks or comments above.
I don't like when comments are on the same line as your code, following the code. It's just so messy looking, and from what I've seen, is not best practice.
-
@Obsolesce said in Looking at Atom and VS Code:
I've never come across a need for virtual space. If I don't have anything written on a line, I wouldn't need a line comment there?
I just tried it in GoLand and I don't like it. If I'm going to a line it's usually so I can edit that line. It's uncomfortable to not jump to the actual data on the line.
-
@Obsolesce said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
@Pete-S said in Looking at Atom and VS Code:
@stacksofplates said in Looking at Atom and VS Code:
As for ctrl+<-/-> just modify the keybindings. Here's an answer for that specific command.
Great thanks. Too bad it's not just a simple setting.
Having the settings in JSON like that is nice because it's easy to back up. There's an extension that syncas all of your extensions and settings to a gist in GitHub.
I still use VSCode a good bit but most of my stuff is done in JetBrains tools now.
Sync is built in to VSCode for a bit now.
I haven't used it for a bit since I started using GoLand.
