Earlier quoted context omitted.
The vscode vim bindings are atrocious. I use them because there's nothing better, but they're bad . Slow, super buggy, and did I mention slow? I hit tab and sometimes instead of inserting a \t, it inserts the letters " ". And it re-runs mypy/flake8/etc whenever I enter or exit insert mode, which I do a ton... so my CPU is constantly pegged. And commands like "2d}" don't delete the correct amount of paragraphs. And on…
Which extension do you use? I don’t use vim mode myself but I vaguely remember seeing a conversation about how, for some reason, the better vim plugin with the most favorites doesn’t appear on the top of the search results, and an inferior one is there instead.
Python in Visual Studio Code
11–20 of 202 posts
Re: Python in Visual Studio Code
#12I am somewhat embarrassed, but also relieved to admit that I switched from vim (nvim to be precise) to VSCode (OMG M$FT!) and am very happy about it. I still use vim bindings as much as I can, but I guess giving up a bit of ideology can benefit one a lot. Although, that is until I start running out of memory on my personal laptop, then it's back to the terminal!
I would really love to ditch more of my nvim setup for vscode, but this bug [1] from 3 months ago absolutely wrecks my productivity. I rely on splits as the primary means to navigate the codebase and having a single cursor position per file is maddening!
The vim bindings aren't perfect and are sometimes slow (you can see a macro insert things character by character) but about on-par with IdeaVim for the IntelliJ side feature wise.
Maybe oni [2] will catch up before vscode fixes their issues but I eagerly await a decent language server modal editing setup.
[1] https://github.com/VSCodeVim/Vim/issues/2688 [2] https://github.com/onivim/oni
Re: Python in Visual Studio Code
#13I am somewhat embarrassed, but also relieved to admit that I switched from vim (nvim to be precise) to VSCode (OMG M$FT!) and am very happy about it. I still use vim bindings as much as I can, but I guess giving up a bit of ideology can benefit one a lot. Although, that is until I start running out of memory on my personal laptop, then it's back to the terminal!
> can benefit one a lot.
What are those benefits?
I tried to switch from vim to VSCode, and it just felt like it confined me. To be fair, I don't "run vim", per say, I run a shell with tmux inside, split horizontally in two, with vim on top, and two shells (a vertical split) underneath. The left shell on the bottom being used for miscellaneous things, and the right one running some kind of live code checking (with visual results also inside vim).
This setup works great for both c, c++, python, haskell, rust, node and any other programming environment I use. I tried getting something along the lines with VSCode, but it confined me, and it felt like it wanted me to do things "its way", instead of letting me decide what I have found out works through years of experimentation. It's the same with jet brains and xcode and visual studie... It doesn't let me do things "my way" but instead forces me to do things its way, which, if I may say, is highly inferior. I have tried their ways and it's not good.
Sorry for the rant.
Re: Python in Visual Studio Code
#14I am somewhat embarrassed, but also relieved to admit that I switched from vim (nvim to be precise) to VSCode (OMG M$FT!) and am very happy about it. I still use vim bindings as much as I can, but I guess giving up a bit of ideology can benefit one a lot. Although, that is until I start running out of memory on my personal laptop, then it's back to the terminal!
> can benefit one a lot. What are those benefits? I tried to switch from vim to VSCode, and it just felt like it confined me. To be fair, I don't "run vim", per say, I run a shell with tmux inside, split horizontally in two, with vim on top, and two shells (a vertical split) underneath. The left shell on the bottom being used for miscellaneous things, and the right one running some kind of live code checking (with vi…
Could you expand on what "Your way" is? I really really like VSCode for Python and never had the nerve to learn VIM, so I'm wondering what you do that causes it to be a fight.
Re: Python in Visual Studio Code
#15Need WSL support for the Python extension! Right now it's impossible to use the Python extensions from within the WSL environment.
Re: Python in Visual Studio Code
#16It was already one of the best out-of-the-box experiences of any Python IDE I've used.
Re: Python in Visual Studio Code
#17I have been following this extension ever since Don Jayamanne joined Microsoft. This has grown by leaps and bounds since then and is a fantastic extension.
I was a little leary when I learned they were tossing out jedi in favor of the VS Python language server. However, after playing with it for a month or so now I can tell that it's a drastic improvement over what's currently in place.
If anybody from the MS team is watching this thread, care to share why you chose to invest in the VS Language Server instead of investing in Jedi further?
Re: Python in Visual Studio Code
#18We want Perl support!
As much as I love Perl, it has a reputation of being exceedingly difficult to parse accurately, hence IDE support will never be great. There's also probably more demand to support hipster languages than last generation's work horses.
Re: Python in Visual Studio Code
#19MS totally dominates tooling. I am so happy with vs code, use it for my angular development as well.
Re: Python in Visual Studio Code
#20We want Perl support!
As much as I love Perl, it has a reputation of being exceedingly difficult to parse accurately, hence IDE support will never be great. There's also probably more demand to support hipster languages than last generation's work horses.
I don't use it since 2000's, but ActiveState's Komodo used to be ok.