3 ms·

> TBH I never really tried neovim, maybe because I like the start screen of vim? The idea of doing something for orphans may be cheezy, but I really like the me

> TBH I never really tried neovim, maybe because I like the start screen of vim? The idea of doing something for orphans may be cheezy, but I really like the message! Ha, I like that! Personally I hide the home screen but I can get behind that and have donated to Vim before. > Also why did you attempt to switch to neovim? I don't feel any limitation in vim. I'd be curious to know why you tried. The first time years ago, was the try out the async stuff, then Vim got it so I switched back. The second time was very recently. I'm primarily a web developer and write a lot of Elixir. The Elixir community is rallied around NeoVim so the experience is quite a bit better. The maintainer of elixir.vim doesn't even write Elixir anymore (though he is very attentive to PRs and issues). I've contributed a bit to it, but ultimately I don't spend a lot of time hacking on Vim anymore (though I do have a todo item to update my vim plugins to make use of viml 9). At the same token, there is a bit of sunk cost fallacy going on in that I know VimL very well. I don't like the idea of having my config in two different languages nor do I like the idea of having to port my whole vimc config (which I know quite intimately) over to Lua. And ya, as you said, I feel no limitation in Vim other than the previously mentioned lack-of-Elixir support. Oh ya, I was also convinced to try it out thanks to this talk [0]. Though, even as a quiet person myself, I found his speaking style very hard to take (but I powered through). I'm actually aware of your Sixel project but never ended up trying it out. I've actually been following you on github for quite some time but---being primarily a web dev---often when I have to compile C on my mac I think "meh, I'll look into this later" and, of course, rarely come back to it. Not a very good reason, I know. And ya, I kind of just switched to zsh years ago because it was "the thing to do". I do write enough shell scripts and never use any zsh-specific features, so I've been thinking of moving back to bash just to try it out again. Thanks so much for your answer! [0] https://www.youtube.com/watch?v=Bt-vmPC_-Ho https://www.youtube.com/watch?v=Bt-vmPC_-Ho

csdvrx 3y ago
> Thanks so much for your answer! You're welcome! I'll try to release more APEs for the sixel related projects because I'd like to make things like https://github.com/bytesnake/vim-graphical-preview/ https://github.com/bytesnake/vim-graphical-preview/ more accessible. A vim that'd use cosmopolitan binaries for the plugins would provide a solution without making everyone compile C code! > The maintainer of elixir.vim doesn't even write Elixir anymore (though he is very attentive to PRs and issues). I've contributed a bit to it, but ultimately I don't spend a lot of time hacking on Vim anymore If the community has moved to neovim and the maintainer of the vim package isn't writing in this language anymore, it may be hard to get a good "out of the box" experience with prepackaged solutions But if the result you get still satisfies you, maybe it's not worth chasing what everyone else is doing with neovim? A minimal hacking around your working vim configuration could get you further, or at least fix your pain points enough to make everything else less important. Also, you can't be certain that what the neovim elixir community find important, their pain points, will be identical to yours: hacking your own solution guarantees you'll be satisfied by it (because if you aren't, you can hack it some more :)

csdvrx 3y ago

> Thanks so much for your answer! You're welcome! I'll try to release more APEs for the sixel related projects because I'd like to make things like https://github.com/bytesnake/vim-graphical-preview/ https://github.com/bytesnake/vim-graphical-preview/ more accessible. A vim that'd use cosmopolitan binaries for the plugins would provide a solution without making everyone compile C code! > The maintainer of elixir.vim doesn't even write Elixir anymore (though he is very attentive to PRs and issues). I've contributed a bit to it, but ultimately I don't spend a lot of time hacking on Vim anymore If the community has moved to neovim and the maintainer of the vim package isn't writing in this language anymore, it may be hard to get a good "out of the box" experience with prepackaged solutions But if the result you get still satisfies you, maybe it's not worth chasing what everyone else is doing with neovim? A minimal hacking around your working vim configuration could get you further, or at least fix your pain points enough to make everything else less important. Also, you can't be certain that what the neovim elixir community find important, their pain points, will be identical to yours: hacking your own solution guarantees you'll be satisfied by it (because if you aren't, you can hack it some more :)