Discussion
I finally made my move to use `vim-classic`, it took no more than 2 lines of configuration and removing some non-compatible plugins I was not using anyway... having less LLM-aided software feels great.
more about the reasoning behind forking vim in this post from Drew DeVault: https://drewdevault.com/blog/Forking-vim/
Thanks @drew and all the collaborators of vim-classic!
@rachel there's nothing much to see just now:
https://git.sr.ht/~esparta/apps
right now it's just the container file and some instructions. But it will have more later on.
@esparta oh yeah that’s quite bare 😁 I misunderstood and thought you’d migrated an existing setup.
@rachel in some capacity I did migrate something, from local to running-in-container; it was interesting to move stuff to the container, which made one my goals finally true: not a single programming language on my host computer, no python, no ruby, no java, no node, no go, no rust...nothing at all.
@esparta hi, can I ask you why your vim is in a Containerfile ? Is it launched with a podman command and not directly from the system ?
@guildem
re: hi, can I ask you why your vim is in a Containerfile ? Is it launched with a podman command and not directly from the system ?
Yes, that's exactly how it works. I've been working on having my system with less and less software installed, moving them all to containers and launching them from a multiplexed terminal.
Why am I doing that? Multiple reasons kind of difficult to explain in a single post, the gist: I love to have control of what's in the host and this is a way to achieve
@esparta thanks for your answer. I'm also interested by containers for day to day apps.
Install bonfire.cafe
Get the full app experience
@esparta @drew I’d love to see your config if you’re happy to share!