3 ms·
I had to start using vscode at a certain level because .net core doesn't have a free debugger (as it seems.) I would have to study vscode-omnisharp source to ge
by bigpeopleareold 8y ago
I had to start using vscode at a certain level because .net core doesn't have a free debugger (as it seems.) I would have to study vscode-omnisharp source to get a clue how the debugger actually works to use it in emacs - something I don't have time for.
But I started to use it more because the autocompletion is nice. It's not perfect, but out-of-the-box experience is nicer.
After a few months though working in it, I want to go back to Emacs, and as such, Emacs is usually running. Magit for example, or being able to split your screen up as needed, or quickly jumping between files, etc. is something that is burnt into my brain. VScode is terrible at these things.
I am watching the lsp-mode and lsp-ui projects. They seem promising because it answers a concern I have : I need to float between projects in different languages and want the typical set of IDE-like features in each one. It would be nice to have a single set of keybindings regardless of language, which vscode excels at now. VScode has a good debugging story out-of-the-box lsp-ui is promising because it is implementing vscode-like features (like peek mode).