3 ms·
I am currently switching from emacs to VS Code. I am using an emacs keymap and I must say, it is wonderful. For Python, I can per project easily select the righ
by Loic 8y ago
I am currently switching from emacs to VS Code. I am using an emacs keymap and I must say, it is wonderful. For Python, I can per project easily select the right virtual environment, the "intellisense" like system is working very well, it is pretty fast and you can customize a lot of it.
I am expecting to slowly move out of emacs for my coding in the next few months.
Emacs will be kept because I have a lot of org-mode files to manage my company at a higher level (lot of tables with formulas to calculate several key indicators). On the longer term, they could be moved as Python notebooks with the rendering in VS Code.
So yes, I do think this is the editor which is going to move a lot of old coders out of emacs/vi/vim.
PS: The added bonus is that I easily get support of Go, Typescript, etc. without the need to "debug my editor". Just install the right extension, done.
- cik 8y agoI have some code that automatically builds virtualenvs for me - in directories (it overrides cd). With vscode, I can change the python interpreter, simply by giving it knowledge of where I store my venvs... with one variable! I can't even tell you how hard that was with VIM.
- lliamander 8y ago> So yes, I do think this is the editor which is going to move a lot of old coders out of emacs/vi/vim. That certainly seems a possibility, though I expect it may be somewhat dependent upon the language used, and whether the community around that language invests enough effort to develop vscode plugins for that language.