gvim
The #gVim #Flatpak, which I am running in #Bluefin, has been grabbing a whole lot of CPU. I only noticed it yesterday, but it could have been going on a bit longer.
Until this is resolved, I'll be using console Vim, which does ship with Bluefin Stable.
I generally prefer gVim because I use the system clipboard a lot, and it's slightly easier with a GUI app. I also use the mouse a bit. That's the kind of Vimmer I am.
I can make it work with console #Vim, and that's probably better for me in the long run.
I would have moved to #Neovim GUI #Neovide, but my .vimrc does not work, and it would be a heavy lift to re-create it.
Until this is resolved, I'll be using console Vim, which does ship with Bluefin Stable.
I generally prefer gVim because I use the system clipboard a lot, and it's slightly easier with a GUI app. I also use the mouse a bit. That's the kind of Vimmer I am.
I can make it work with console #Vim, and that's probably better for me in the long run.
I would have moved to #Neovim GUI #Neovide, but my .vimrc does not work, and it would be a heavy lift to re-create it.
I just spent a half-hour hacking in the #Neovide (GUI version of #neovim) #Lua config file, and I have figured out abbreviations and custom keymapping, which means I can move my "production" editing from #gVim to Neovide with a clean Lua config file.
Do I need to move away from gVim/#Vim? I'm not sure, but we're in this game to try new things, right?
Is it worth it to move from Vimscript to Lua?
Do I need to move away from gVim/#Vim? I'm not sure, but we're in this game to try new things, right?
Is it worth it to move from Vimscript to Lua?