Earlier quoted context omitted.
Emacs doesn't do go to definition? Eeek
Visual Studio Code itself doesn't either.
Visual Studio Code 1.8
191–197 of 197 posts
Re: Visual Studio Code 1.8
#192Re: Visual Studio Code 1.8
#193Earlier quoted context omitted.
Oh, not sure how I missed this! I'll have to try it out EDIT: On trying it out, it seems to have reasonable support for most of the editing functionality, but the shortcuts for handling split buffers (C-x 0, C-x 1, C-x o, etc.) is completely non-existent. I'm unsure right now whether I'd be able to define them on mine own or whether I'd be willing to stick with it if I couldn't.
If it's missing functionality you need you could request by filing an issue to https://github.com/hiro-sun/vscode-emacs
For anyone interested: https://gist.github.com/saghm/6f97aea92029fec62067e658c6f02f...
Re: Visual Studio Code 1.8
#194I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…
> - Intellisense is immediately superior to anything I've used in EMACS. For JS maybe. Irony with irony-clang is the best C++ autocomplete I've found. VSCode's C++ Intellisense is crap.
Re: Visual Studio Code 1.8
#195I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…
> Moving around the code with just a keyboard (ctrl-v and the sort).
That is something I have missed in pretty much every IDE I have ever used, except OpenWatcom's, which allows to use vi-keybindings. (Okay, so Eclipse supports Emacs-ish keybindings, too, but it felt really weird using those.)
I think, there is a plugin/package for VSCode that implements emacs-style keybindings, but I could not get it to work properly. :-(
Re: Visual Studio Code 1.8
#196I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…
For the IDO part: If you open a folder in VS Code, then you can use Ctrl+P or Ctrl+T (I keep forgetting which), and that allows you to type part of the file name, and then it will find it. The best is, it searches the entire subtree of the folder you opened.
Re: Visual Studio Code 1.8
#197I recently moved from EMACS (after using it for ~10 years & ~6 languages) to VSCode. There are loads of things that I miss but overall it's been a fairly smooth transition. I'm moving because I spend most of my time writing javascript and felt that no combination of emacs modes allowed me to keep up with a proper IDE. Emacs is a tool to learn once and use for a lifetime (and I will continue to use it for other editin…
> - Intellisense is immediately superior to anything I've used in EMACS. For JS maybe. Irony with irony-clang is the best C++ autocomplete I've found. VSCode's C++ Intellisense is crap.