Are there any VS Code users around who used to use either Emacs or Vim who might share a few things they feel VS Code does better? I'm curious about these modern editors and sometimes wonder what they have to offer besides possibly being easier to learn (an advantage I'm not interested in).
Visual Studio Code 1.6
211–220 of 231 posts
Re: Visual Studio Code 1.6
#212Earlier quoted context omitted.
I'm currently switching from gvim to vscode and back again every five minutes, in order to use vscode's debugger --- it's gdb integration is the best I've seen bar none [1][2]. If the vim emulation was good enough, I'd switch in a moment. Which, unfortunately, it's not, for me: the biggest omission is shift-Y/shift-P for yank and paste, which I use constantly, but there's holes everywhere. (Also, the way the vscode's…
Hi! I'm one of the core developers of VSCodeVim. Shift-Y and Shift-P absolutely work for me, so please report on our issues page if they continue to not work for you: https://github.com/VSCodeVim/Vim/issues I would also be really interested to hear about the other holes that you're running into. Always trying to make a better Vim experience for you :)
Hi John,
I've spoken with a few of the devs in our team having trouble with VS 2015 update 3 crashing. They'd love to switch to VSCode but ask:
1. When is there going to be decent C#/razor-intellisense, a razor generator ?
2. Will there be TFS integration (not git)?
Re: Visual Studio Code 1.6
#213Earlier quoted context omitted.
You should submit an issue with a repro: https://github.com/microsoft/vscode-go Go plugin is very much actively maintained.
Good point. I had been meaning to do that for a while. Thanks for the nudge: https://github.com/Microsoft/vscode-go/issues/521
Update: found out it was because I needed to run `go get` or `go install` to have the subpackages listed in my $GOPATH/pkg directory.
Re: Visual Studio Code 1.6
#214Are there any VS Code users around who used to use either Emacs or Vim who might share a few things they feel VS Code does better? I'm curious about these modern editors and sometimes wonder what they have to offer besides possibly being easier to learn (an advantage I'm not interested in).
Vi/Vim user since 1992. Flirted with emacs every so often. I haven't used Vim in 9 months since installing VS Code. Here's why:
1. IntelliSense support is the best outside of Visual Studio itself. 2. Integrated debugging (currently use C#/mono and Python debuggers a lot) 3. Great git integration. Best "GUI" client around. (advanced git features are not provided, but everyday stuff is really well done) 4. Visually appealing. Not saddled with a terminal heritage.
Just to name a few. Yes, Vim and Emacs have all of these, to some degree. But VS Code does them all better (IMO).
It's fun to use. There's a lot to discover, but there's enough there to be productive right from the start.
Re: Visual Studio Code 1.6
#215Are there any VS Code users around who used to use either Emacs or Vim who might share a few things they feel VS Code does better? I'm curious about these modern editors and sometimes wonder what they have to offer besides possibly being easier to learn (an advantage I'm not interested in).
Vi/Vim user since 1992. Flirted with emacs every so often. I haven't used Vim in 9 months since installing VS Code. Here's why: 1. IntelliSense support is the best outside of Visual Studio itself. 2. Integrated debugging (currently use C#/mono and Python debuggers a lot) 3. Great git integration. Best "GUI" client around. (advanced git features are not provided, but everyday stuff is really well done) 4. Visually app…
Thanks! It seems that most of those advantages are not directly about text editing but more about being a better IDE. I guess that for someone like me, that uses Emacs mostly for writing prose and for file management, and only occasionally for programming, the things you mention don't sound as attractive (and when coding I never use a debugger, which is probably a mistake on my part).
About git: have you tried magit for Emacs?
Re: Visual Studio Code 1.6
#216Earlier quoted context omitted.
Vi/Vim user since 1992. Flirted with emacs every so often. I haven't used Vim in 9 months since installing VS Code. Here's why: 1. IntelliSense support is the best outside of Visual Studio itself. 2. Integrated debugging (currently use C#/mono and Python debuggers a lot) 3. Great git integration. Best "GUI" client around. (advanced git features are not provided, but everyday stuff is really well done) 4. Visually app…
Thanks! It seems that most of those advantages are not directly about text editing but more about being a better IDE. I guess that for someone like me, that uses Emacs mostly for writing prose and for file management, and only occasionally for programming, the things you mention don't sound as attractive (and when coding I never use a debugger, which is probably a mistake on my part). About git: have you tried magit…
Yes, I have used magit while trying to find some love for emacs. It's fine. But I still prefer VS Code's git integration. It's the simplest client I've seen. I don't mind using the command line for git, but if I'm in the editor, I can do anything I need to do for my daily workflow with keyboard commands or point and click, whichever mood I'm in.
And as far as text editing, there is a lot that VS Code provides for getting around and moving around text and windows and files. Multiple cursors and syntax-aware selections provide me what I loved about Vim (macros and text objects). And now I don't drive myself nuts hitting the escape key in every other application where I type some text.
Re: Visual Studio Code 1.6
#217Re: Visual Studio Code 1.6
#218Earlier quoted context omitted.
Hi! I'm one of the core developers of VSCodeVim. Shift-Y and Shift-P absolutely work for me, so please report on our issues page if they continue to not work for you: https://github.com/VSCodeVim/Vim/issues I would also be really interested to hear about the other holes that you're running into. Always trying to make a better Vim experience for you :)
Hi John, I've spoken with a few of the devs in our team having trouble with VS 2015 update 3 crashing. They'd love to switch to VSCode but ask: 1. When is there going to be decent C#/razor-intellisense, a razor generator ? 2. Will there be TFS integration (not git)?
I'm just the developer of VSCodeVim. I don't work on VSCode at all outside of that, so unfortunately I can't help you there. :)
Re: Visual Studio Code 1.6
#219Earlier quoted context omitted.
Hi! I'm one of the core developers of VSCodeVim. Shift-Y and Shift-P absolutely work for me, so please report on our issues page if they continue to not work for you: https://github.com/VSCodeVim/Vim/issues I would also be really interested to hear about the other holes that you're running into. Always trying to make a better Vim experience for you :)
I was actually the one who submitted the feature request which you closed --- I'll reopen this. Thanks! Update: no, I can't reopen it, so I'll open a new bug.
...aaaand they've fixed it and pushed out a new release. Thanks very much!
Re: Visual Studio Code 1.6
#220Is there a good VS Code extension / built in support for function / method list on a separate side bar?
Something similar to Structure view in Webstorm or Function List in Notepad++?
I learned that Ctrl-Shift-O will show functions but it is a not a permanent view.