passthejoe
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.
Feb 28 at 4:40pmWeb
Show threadpassthejoeFeb 28
@[email protected] Now ... If I could figure out programmable/editable macros in #Neovim, I'd be off to the races. Same for #Helix.
Show threadpassthejoeFeb 28
@[email protected] I might also try gVim in a Distrobox. We have a lot of choices in Linux in general and Bluefin in specific.
Show threadpassthejoeFeb 28
@[email protected] TBH, it's magic how the base system, Brew and Distrobox don't step all over each other in #Bluefin. How do they do it?
Show threadJorge CastroFeb 28
@passthejoe https://jvns.ca/blog/2016/10/10/what-even-is-a-container/
What even is a container: namespaces and cgroups

What even is a container: namespaces and cgroups

Julia Evans
Show threadpassthejoeMar 2
Great link. There's a lot to learn.
Show threadHyde 📷 🖋 Mar 1

@passthejoe about the vim system clipboard :

% vim --version | grep clipboard

If you see +clipboard or +xterm_clipboard, you are good to go. If it's -clipboard and -xterm_clipboard, you will need to look for a version of Vim that was compiled with clipboard support. On Debian and Ubuntu, to obtain clipboard support install the packages vim-gtk or vim-gnome.

I don't know on Bluefin though ...

Show threadpassthejoeMar 1
I just got an update for the g/Vim Flatpak, and so far the CPU problem seems to be resolved.

I'm in gVim most of the time, so this is excellent news.