I tried out VSCode a year ago coming from emacs, but I couldn't bring myself to get started because I missed Emacs' helm-find-files too much. VSCode needing to have directories 'added' before it can navigate to them, and not really showing you the directory tree structure was already a dealbreaker for me.
To be honest, I was a little afraid when I commented that you'd point out some simple thing I had missed, and that I would then feel compelled to give VSCode another try. So thank you for helping me keep my emacs security blanket.
Comments
14 year Emacs user.
1. Fuzzy command completion like Emacs helm-M-x
2. Remote shell integration that is better than Emacs TRAMP.
3. Works more reliably than Emacs.
4. LSP support.
5. Works on Mac, Windows, Linux.
6. Can cajole coworkers into using it and thus have deeply integrated tooling in our workflow that applies to everyone.
Things I miss: 1. Org mode (particularly org-capture)
2. eval-region
3. helm-sloop
I tried out VSCode a year ago coming from emacs, but I couldn't bring myself to get started because I missed Emacs' helm-find-files too much. VSCode needing to have directories 'added' before it can navigate to them, and not really showing you the directory tree structure was already a dealbreaker for me.
Yes, I admit this is a pain-point I have no solution to.
My current project is mostly contained to not very many sub projects, so it hasn’t been an issue.
To be honest, I was a little afraid when I commented that you'd point out some simple thing I had missed, and that I would then feel compelled to give VSCode another try. So thank you for helping me keep my emacs security blanket.
Agreed on org mode. I'm more of a vim + vscode user, but I did try spacemacs once and org mode was a big take away for me.