4 ms·
idk, let alone vim, even native emacs is 1000x better then sublime text and vscode, people who use vscode are just not the kind of people who would be interest
by teitoklien 5y ago
idk, let alone vim, even native emacs is 1000x better then sublime text and vscode,
people who use vscode are just not the kind of people who would be interested in using emacs, and that's fine.
- kstrauser 5y agoI disagree. I used Emacs for a couple of decades until I hopped onto VS Code. The Python setup was particularly nice, as it did everything I hoped for with no special configuration. That said, Microsoft’s gotta Microsoft, and between their GitHub shenanigans and their proprietary language server, I’ve switched back to Emacs. BTW, turns out elpy has been coming along nicely and offers nearly as nice of an out-of-the-box experience as VS Code, and is better in some ways.
- bee_rider 5y agoSimilar experience with doing the vim -> VS Code switch. Didn't end up actually wanting the product, but the act of temporarily switching to a different editor made me double check what was available at home. For example, modern editors have a neat feature where they'll highlight a variable everywhere if you put your cursor on it. Nice to have, didn't think to look for it, there's a vim plugin that does it.
- sys_64738 5y ago> For example, modern editors have a neat feature where they'll highlight a variable everywhere if you put your cursor on it. Nice to have, didn't think to look for it, there's a vim plugin that does it. This sounds like pressing '*' over a keyword in vim.
- bee_rider 5y agoHonestly, I thought the difference was that the plugin was more selective about distinguishing between things like object.field and a variable that just happened to be called field but when double checking I wasn't able to get any clever behavior out of it.
- sys_64738 5y agoInteresting. Not sure * has such semantics. Must check next year.