Live data from Hacker News

Python in Visual Studio Code

blogs.msdn.microsoft.com

61–70 of 202 posts

Re: Python in Visual Studio Code

#61

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…

The author of vscodevim is working on a new extension that uses NeoVim's remote UI client protocol. Accuracy and speed will hopefully go way up when that is finished. Unfortunately progress appears to have stalled somewhat. https://github.com/Chillee/VSCodeNeovim

I went back to "vanilla" NeoVim solely due to the slowness of the VSCode Vim plugin. Been watching the repo you linked a couple of times a month and always disheartened that nothing seems to happen.

Re: Python in Visual Studio Code

#62
I was born and raised in Emacs, but over the years switched to Vim (on Amiga) and used it ever since. Occasional stints came and went (UE32, Sublime...), but vim remained. It still does, but used to too. VS Code, on the other hand, is excellent for Javascript. Whenever I need to do JS, VS Code is the tool to do it. Along with Brackets for quick proto/live preview (something VS Code doesn't do as well).

Vim is still my goto (heh, heh!) 'IDE' for C. I still haven't explored, in-depth, going towards Spacemacs for C... but my vim setup is now so well-honed for everything C that I'm not sure what would be the benefit of jumping on top of anything else. Doesn't seem worth it, except for debugging, which I do per-platform anyways.

In any case, VSCode for JS is THE tool, along with Brackets for live preview when making a proto.

Re: Python in Visual Studio Code

#63
What I'm hoping for, for all langauges and runtimes, is some global opt-in to WSL. If I have node or python installed on WSL, I would love it if the Windows version of VSCode could act as if it were the Linux version.

Re: Python in Visual Studio Code

#66
post #54
post #24

I've been using VI since the 90's and VIM since... well the 90's. VSCode is the first IDE I've been able to live, and happily. It blows my mind. I have a tonne of tooling around automated python environments, vim plugins (now vscode plugins), tasks - and it's made the whole thing significantly more 'unixy' than it was before. And to think - MSFT! I have git hooks for my homedir's dotfiles that automatically look to s…

Just out of curiosity, what are some of the tasks that you run in vscode ? I've never found a real use for them, so I want to know what other people use them for.

[deleted]

Re: Python in Visual Studio Code

#67
post #24

I've been using VI since the 90's and VIM since... well the 90's. VSCode is the first IDE I've been able to live, and happily. It blows my mind. I have a tonne of tooling around automated python environments, vim plugins (now vscode plugins), tasks - and it's made the whole thing significantly more 'unixy' than it was before. And to think - MSFT! I have git hooks for my homedir's dotfiles that automatically look to s…

What vim plugin(s) do you use? I remember installing one but the emulation did not quite work for jumping into code definitions and back (it'd jump, but going back wouldn't work correctly), so I moved back to pycharm for the time being (vim emulation worked better there for me).

Re: Python in Visual Studio Code

#68
post #64

Crazy question: Since Microsoft bought GitHub, would it make sense to merge VSCode and Atom at some point, keeping the best of each one?

I never even thought about that. I had such high hopes for Atom and the speed hit was real at first just as I thought and figured nothing would beat my Vim setup. Then someone on HN stated that VS Code was really good and I just went back to my i3 and rsvt setup and laughed. Now I use VS Code non-stop in Linux. I went back to Atom and was underwhelmed compared to VS Code's community.

Re: Python in Visual Studio Code

#70
post #52

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…

What's the bug that you have with `2d}`? It seems to work fine for me. There shouldn't be any reason that it reruns save upon entering/exiting insert mode; are you sure you don't have some kind of keybinding/other setting that's autosaving for you? The ` ` issue is kind of a pesky race condition that's most likely exacerbated by VSCodeVim running slowly on your computer. Speaking of it running slowly, I would argue a…

I use VSCodeVim every day and I just wanted to say thanks for your work. You made the switch to VSCode a lot easier for a lot of people.
Post reply on HN