I used that settings for a few years, then tried to move entirely to vim, and now I'm very happy with vscode + vim. I like vim as a touch typer, I think it's a setting that minimize end motions. It's also very convenient in the terminal. On the other hand, I think it's not convenient as an IDE: too many shortcuts, clumsy integration with LSPs, especially when you need to work with different languages. For me it works…
For all the space/doom emacs users check out VSpaceCode it's basically all the space emacs shortcuts in vscode and i can't live without it anymore.
I used that settings for a few years, then tried to move entirely to vim, and now I'm very happy with vscode + vim. I like vim as a touch typer, I think it's a setting that minimize end motions. It's also very convenient in the terminal. On the other hand, I think it's not convenient as an IDE: too many shortcuts, clumsy integration with LSPs, especially when you need to work with different languages. For me it works…
For all the space/doom emacs users check out VSpaceCode it's basically all the space emacs shortcuts in vscode and i can't live without it anymore. https://vspacecode.github.io/
Just use vim. Yes, emacs has a lisp engine, but so does nvim[1]. Really, though, using vim properly means that it doesn't need to swallow the kitchen sink[2]. Just use vim. 1: https://github.com/Olical/aniseed 2: https://blog.djha.skin/p/emacs-users-im-okay-i-promise/
Emacs vs. Vim is a meme. You wrote a whole blog post as a PSA over a meme.
I understand what you're saying but the feelings were real. I kept getting frustrated because I would comment and say you know vimm is not that bad and I would just get piled on by emacs users saying no come back it's okay just try us again and it was annoying so I wrote a response to them up as a blog post so I wouldn't have to write my opinion twice.
I can't work out what is actually wrong here - there appears to be very little detail, would you mind explaining?
False warning about unused definition 'salary' when it is actually being used.
Thank you for explaining - I didn't think to click on the thumbnail as I thought the snippet _is_ the expanded thumbnail.
The way I see/read it: it _isn't_ being used in respect to nothing _reads_ it, except within the calculation to raise - there's nothing that reads the result of the raise. It's warning you that you are (potentially) needlessly capturing state. I agree it's a valid warning (for that specific example.)
I appreciate it is just an example to demonstrate the issue but I am unable to deduce a scenario where that wouldn't be a valid warning.
There's also meow-mode[1], which isn't a vim emulator as such, but it is a different modal editing layer for Emacs which is a lot faster and has a lot of neat ideas. It doesn't interfere w/the stock keybinds at all though, which is much nicer imo (I use a 'hybrid' editing style generally) 1: https://github.com/meow-edit/meow
There's also Boon which I like quite a lot but I opted against using mostly because of all the places I would need to type where I wouldn't have access to Boon unless I ported it (a plan I assure you but one lumped behind 1,000 other projects TODO).
False warning about unused definition 'salary' when it is actually being used.
Thank you for explaining - I didn't think to click on the thumbnail as I thought the snippet _is_ the expanded thumbnail. The way I see/read it: it _isn't_ being used in respect to nothing _reads_ it, except within the calculation to raise - there's nothing that reads the result of the raise. It's warning you that you are (potentially) needlessly capturing state. I agree it's a valid warning (for that specific exampl…
'salary' is part of the constructor's body and the constructor is being used, it shouldn't warn. Look how it just warns about 'salary' but not about 'name', in the image, only 'salary' is gray out. It's not even consistent.
There's also meow-mode[1], which isn't a vim emulator as such, but it is a different modal editing layer for Emacs which is a lot faster and has a lot of neat ideas. It doesn't interfere w/the stock keybinds at all though, which is much nicer imo (I use a 'hybrid' editing style generally) 1: https://github.com/meow-edit/meow
What I like about Meow is that it replaces a lot of stuff for me -- Evil, evil-collection, general, expand-region, and maybe something else. And it does not seem to be as invasive. But the killer feature is meow's macro system
What I like about Meow is that it replaces a lot of stuff for me -- Evil, evil-collection, general, expand-region, and maybe something else. And it does not seem to be as invasive. But the killer feature is meow's macro system
> That being said, I wonder if I wouldn't be better off moving away from vim entirely That's a surprising sentence to read, as someone who's also used to vim (although I've moved from vim to emacs+evil and not the other way around). I have some gripes with my emacs+evil setup, just as I had some gripes with my vim (and then neovim) setup. But none of those gripes were related to the actual text editing, but rather ma…
> That's a surprising sentence to read, as someone who's also used to vim Well, I feel modal editing is "comfortable", as in easy on the fingers. But overall, I'm also quite fluent with the mac os shortcuts. Maybe it's just a matter of learning the few things I don't know how to do without vim and I'd be equally happy. The added bonus would be to have a simplified set up that would work in every contexts where vim is…
Even on windows, while there are some obvious editing benefits with Vim mode, there's so much you can do with modern shortcuts. VS Code is customizable as hell, and the mouse is still an invaluable tool. With a TKL keyboard, I have no issues reaching for it and then resting my hands back on my keyboard without looking down or searching for it.