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…
Python in Visual Studio Code
161–170 of 202 posts
Re: Python in Visual Studio Code
#162VSCode is not emacs, but it's not bad at all.
Re: Python in Visual Studio Code
#163I'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…
One thing I forsee being a problem is that one of my projects is a side project, that I usually work on from the couch at home, using my chromebook sshed into a box running vim. So, I can't run vscode in that environment. No biggie though, I can drop to vim for that.
Re: Python in Visual Studio Code
#164Earlier 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…
Re: Python in Visual Studio Code
#165Need WSL support for the Python extension! Right now it's impossible to use the Python extensions from within the WSL environment.
- https://github.com/Microsoft/vscode-python/issues/67
And the VS Code team was asking for folk to interview regarding WSL integration:
https://forms.office.com/Pages/ResponsePage.aspx?id=v4j5cvGG...
(Full disclosure: I work at Microsoft, but in other teams, and am eagerly waiting for the day I can use WSL pyenvs)
Re: Python in Visual Studio Code
#166Earlier quoted context omitted.
> Intellij IDEs are really fast I would strongly dispute this. I love the JetBrains IDEs and have been using IntelliJ IDEA for many years, but performance in general is definitely not one of its strong suits (though it has improved significantly over the years). IntelliJ just feels very sluggish to me, and regularly lags and hangs on our (rather large) work codebase. Anything that causes the IDE to start indexing tak…
Are you sure you're not just running out of heap space? That problem appeared really quickly when we migrated our devs to IntelliJ, and slowed it down to a crawl. The default 750MB are just not enough for projects with 5000+ Classes.
Re: Python in Visual Studio Code
#167Earlier quoted context omitted.
I mean, it sounds like to me vscode has nothing to offer you, if your desktop (i.e. what we see when we look at your monitor) remains so static (in a positive sense). I find vscode more useful than vim because I can quickly and easily swap out the pieces of environment I need. Need a terminal real quick? Ctrl`, command, ctrl` again and poof it's gone, with nothing in front of me but my code. Need git real quick? Ctrl…
> I find vscode more useful than vim because I can quickly and easily swap out the pieces of environment I need. Need a terminal real quick? Ctrl`, command, ctrl` again and poof it's gone, with nothing in front of me but my code. Need git real quick? Ctrl shift g. Need one more tab? Another? Ctrl \, and so on. I'm able to do all of these things too with my setup, although it's not vim driving my setup, it's tmux. Usi…
For a while I was running (g)vim8 with the built in :terminal - but I had some character issues with meta mapping (so typing tings like ~ on my Norwegian keyboard layout was a chore). Qt neovim didn't have these issues, whatever caused them - but I also switched back to a tiling wm (i3) - and I'm not sure if screen in neovim term really is better than a neovim on one side and a terminal w tabs on the other.
What I will say is that vim8 has a "better" terminal out of the box than neovim (that realized the idea first) ;in vim switching out of insert mode is easy and allows real nice copy to buffer - say to copy from a repl, and switch windows to paste into a file.
The limit of one (two) x11 clipboards is a bit of a pain, but with setting the x clipboard to default copy/pasting between vim and the rest of the world becomes pretty painless.
Anyway - point being, vim/neovim has great support for managing terminals - but I'm not convinced it's a great idea.
Re: Python in Visual Studio Code
#168Since the 80s and BRIEF (anyone remember that?) I have relied on record/play keyboard macro with every programmer's editor I've used. This fundamental feature is missing in VSCode, sadly it's a complete showstopper for me. I get the impression that VSCode's architecture makes this difficult or impossible to implement as an extension.
Re: Python in Visual Studio Code
#169Earlier quoted context omitted.
not op, but i use ctrlp.vim for everything. feels a lot better than most things.
Yeah, exactly. I use NERDTree for discovering new projects, but other than that, I use a fuzzy matcher for files and buffers. I used ctrlp for years, but recently switched to fzf because it's just faster.