That does bum me out. I played around with Tangled before their recent 1.0/site redesign and it felt a bit locked up. I could run the "knot" to host my (public only) content but not the viewer. I think this story has improved now, I hope so.
I do think there is maybe some better outcome where the forge is explicitly started as a decentralized space, the lock-in is inherently not "built in" for later value extraction and I have no issue with VC wanting to make their money back via enterprise support, ci, etc if the 80% use case of view/share/follow is actually distributed and free as in freedom.
They appear to support "push" mirroring, but not "pull" mirroring. This appears to be a technical restriction, not an ideological one:
> Why can't I mirror repositories from other code-hosting websites?
> Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.
> If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror.
I think the mini part is that each is fully independent and you can pick and choose which to use individually. I currently use 4 mini.* plugins out of the 10 plugins I use and am happy with what they do.
I'd say its more about the size/scope of each plugin rather than the number, and that you can use the whole thing like an nvim distro or pick and choose what you like and bring them to your own config
Not everyone needs the same 4 plugins as you and this is a very nice set of plugins, each parsimoniously designed to have minimal configuration needed. The whole repo is a few megabytes.
The author is a neovim core contributor and I find his approach to plugins very compelling.
First time I hear about tangled and I love it. Really nice to see new git hosting solutions appear.
Wait until you hear it is VC funded as well
That does bum me out. I played around with Tangled before their recent 1.0/site redesign and it felt a bit locked up. I could run the "knot" to host my (public only) content but not the viewer. I think this story has improved now, I hope so.
I do think there is maybe some better outcome where the forge is explicitly started as a decentralized space, the lock-in is inherently not "built in" for later value extraction and I have no issue with VC wanting to make their money back via enterprise support, ci, etc if the 80% use case of view/share/follow is actually distributed and free as in freedom.
> These modules improve your text editing experience. Start with 'mini.ai', ...
> mini.ai | Extend and create a/i textobjects
what a fun name.
It's "around/inside" for curious non-vim users. As in insert-around-this-word or select-inside-quotes.
Isn't Codeberg against mirrors?
They appear to support "push" mirroring, but not "pull" mirroring. This appears to be a technical restriction, not an ideological one:
> Why can't I mirror repositories from other code-hosting websites?
> Mirrors that pull content from other code hosting services were problematic for Codeberg. They ended up consuming a vast amount of resources (traffic, disk space) over time, as users that were experimenting with Codeberg would not delete those mirrors when leaving.
> If you need a mirror, you can create manual mirrors by adding multiple remotes to your local repository and using git push --mirror.
Source: https://docs.codeberg.org/getting-started/faq/
it looks like it's hosted on github and now tangled?
Why? And does tangled support CI/CD like GH Actions?
Yeah, Tangled supports CI/CD. It has this lovely concept of 'Spindles' which lets you host it all yourself.
https://tangled.org/docs/spindles/
I think it is a mirror. The github repo still exists, and I assume is where CI is run.
Well, GitHub had an outage pretty much every single day last week, so there’s one reason
"Mini.nvim"...
I am looking at my vim config with my 4 plugins.
What's "mini" about your "45+ independent Lua modules" ?
I think the mini part is that each is fully independent and you can pick and choose which to use individually. I currently use 4 mini.* plugins out of the 10 plugins I use and am happy with what they do.
I'd say its more about the size/scope of each plugin rather than the number, and that you can use the whole thing like an nvim distro or pick and choose what you like and bring them to your own config
A side note is that nvim does incorporate things upstream natively.
I believe "gcc", a la tpope, is now default part of nvim (not as a plugin just as a thing).
Also treesitter.
Even package management is built natively into nvim now (and nvim's implementation is supposedly inspired by mini's).
Not everyone needs the same 4 plugins as you and this is a very nice set of plugins, each parsimoniously designed to have minimal configuration needed. The whole repo is a few megabytes. The author is a neovim core contributor and I find his approach to plugins very compelling.