481–490 of 537 posts
Earlier quoted context omitted.
This reads so much like that macho programmer who wrote everything in assembler from a few decades ago. I will keep using Sublime Text. No need to suffer needlessly.
This is pretty ironic, given that Sublime Text is basically dead in terms of community, number of users, etc and definitely isn't a full IDE.
Earlier quoted context omitted.
> Was that expressly written to parody Vim? Yes. The advice to turn the yoke upside down is supposed to reference remapping Caps Lock to Escape, without which Vim destroys your pinky on a standard keyboard. But it's the choice of professionals, so what can we do?
Remapping Caps Lock to Ctrl is a life changer in any environment. Seriously, just try it. It makes a useless key actually useful.
A true IDE layer for neovim. The best part is that the developer(Folke) is very active with development and basically helping with all sorts of problems- the other day, I opened a pull request and it was resolved within hours.. Thank you Folke for the amazing work around neovim not limited to lazyvim.
Earlier quoted context omitted.
This reads so much like that macho programmer who wrote everything in assembler from a few decades ago. I will keep using Sublime Text. No need to suffer needlessly.
This is pretty ironic, given that Sublime Text is basically dead in terms of community, number of users, etc and definitely isn't a full IDE.
Earlier quoted context omitted.
> Was that expressly written to parody Vim? Yes. The advice to turn the yoke upside down is supposed to reference remapping Caps Lock to Escape, without which Vim destroys your pinky on a standard keyboard. But it's the choice of professionals, so what can we do?
Aaaactually… professionals map jj to Esc. JJ Abrams disagrees, though.
Earlier quoted context omitted.
What about control+c? Also, I've never used vim without remapping `jj` to .
Ctrl+C and Esc do not behave the same in all contexts. The correct replacement for Esc is Ctrl+[. What if you need to type `jj`? Not uncommon to do so while writing math or physics papers. a_{jj}
Earlier quoted context omitted.
The thing about vim and emacs is that both of them, out of the box, suck. BUT, what they both offer better than anything else, is the ability to gradually modify them to match what your brain needs. I 100% agree with your hyperbolic "200 keybinds to make a view component" But that's ...that's not how it works unless that's what your brain wants. With ALL editors you eventually encounter "ugh, this is frustrating" or…
> You _can_ accept pre-made defaults In my case, I'd prefer to do so. I'm a different use-case though, I'm a server admin so I want to be as comfortable with bare-bones defaults as possible so that I can jump on any server and just use Vim (or sometime just vi!). I can't afford the time it would take to set up a custom config on every server in every environment, so the most I need is a basic .vimrc that has `set num…
LunarVIM has been a bit tricky, mostly related to upgrades around LunarVIM, usually neovim updates. But, the capabilities of having Language Server in vim have been so refreshing! Particularly when working with Python 2 code to bring it up to Python 3, pretty much just follow what Language Server says.
When it gets right down to it, there are only a couple little tweaks from my old setup I want to carry over, everything else I want to go back to using defaults (places where I've diverged my own functionality) and stop pushing around a poorly maintained manual config that gives me 10% of what Lunar or similar gives.
Earlier quoted context omitted.
Can you actually explain how it's suboptimal UX, and what I could be doing better. I want a simple IDE, not suboptimal bloat. I don't need 200 keybinds to make a vue component. Just because you have a bunch of custom quirks doesn't mean that I do.
The thing about vim and emacs is that both of them, out of the box, suck. BUT, what they both offer better than anything else, is the ability to gradually modify them to match what your brain needs. I 100% agree with your hyperbolic "200 keybinds to make a view component" But that's ...that's not how it works unless that's what your brain wants. With ALL editors you eventually encounter "ugh, this is frustrating" or…
Earlier quoted context omitted.
You’re absolutely right that this can happen, but wrong that it is representative. Let’s take all the serious vim users in the world. How many have this kind of plugin hell experience? A tiny percentage. Serious vim users don’t try to create a kitchen sink IDE. They start with a vanilla base and with their way up, including just the features that are important to them. Starting with something like LazyVim is fine too…
I agree that vim is a perfectly fine text editor. Yet half the (neo)vim people in this thread are yelling it's the One True IDE that can, in fact, do everything, and if you are using VSCode or IntelliJ or whatever then you must be a noob or too lazy to invest time in your tools.
Many people complain about the time you need to have a proper vim. In computer security, I learnt to make my own tools, to develop my own script that match what I want to do/scan. For vim, this is exactly the same. I started with Python so my vim became the best Python IDE (for me) and that's all. What I said to junior dev is "Here my vim conf, you are allowed to copy/paste only what you understand". Then I did some…
what's the current recommended package manager for vim? I used to use vundle but that seems to be unmaintained/deprecated and has broken on recent installs.