Or worse yet, even realize they can beyond a sort of intellectual acknowledgement of the possibility.Īt that point, they might as well be using Atom, ST, or another GUI editor. They might make tweaks in the future, but they might never dig deeper to really customize it. With a configuration that's so tightly written (not sure if that's the best way to put it), I kind of felt like I was setting them up to use vim, but not be vim users.
They have some fairly well-defined conventions of their own, and while that allows some pretty neat stuff, it struck me as limiting for the beginner. I was recently talking to a friend who was thinking of switching to vim, and to be honest, I was a bit unsure about recommending one of those configurations when asked for a good default. Spacemacs/SpaceVim/SpaceNeovim are some impressive default experiences, but they achieve that through large, complex config files that make it difficult for beginners to parse. Pretty much everything can be customized or tweaked, but it's mostly on you to explicitly do so. That's the tradeoff with editors like emacs and vim, unfortunately. Kind of the nuclear option, and largely a result of a failure to adequately comment my dotfiles. I've recently started to rebuild them to try and simplify things, cut out the unused but "neat" stuff I added over time, etc.
I had a lot of junk in my config files from when I started learning vim seriously, a lot of which I never really used. Have you considered splitting up your vim config into multiple files, particularly for the conditional stuff? It doesn't cut down on the size of configurations as a whole but it does make it a bit easier to approach.
0 kommentar(er)
