Thanks. Hope you like it.
Thanks. Just a small correction. The API isn't really REST, it's REST-ish but probably closer to JSON-RPC.
Hope you like it.
That could be, but I don't think that it should be relied upon. The shortener itself can execute malicious code, so that kind of security is, in my opinion, essentially theatre. I'd just say that don't click on links that you don't trust.
This project is for own use/use with friends/family/internally in an org etc., where trust isn't an issue. Of course, I cannot stop anyone from using it in any other way that they see fit. It can help shorten annoying long links for ease of sharing, but that's it.
Wayback machine seems to be unable to save this.
I really like Feeder.
Here's a pretty small project that's still practically useful, at least to me.
I decided to migrate to zpack.nvim instead. Got to keep my old lazy config with minimal changes, and it works pretty great. I guess I just like the modular nature of my setup, and also I just went through a major rewrite last month, don't wanna redo it just yet.
I've been thinking about moving away from nvim-treesitter for this. There seem to be some alternatives already, like tree-sitter-manager. Or I can probably just get it to work without any plugins.
The only thing that I'm worried about are the features provided by nvim-treesitter-textobjects. Has anyone been able to replicate those in native neovim, or even using some other plugin that's not dependent on nvim-treesitter?
Edit: There seems to be some interesting recent development.
Just to add to it, there's a thin wrapper around it called zpack that's basically a drop-in replacement for lazy.
I'm not the dev, but I've migrated from lazy to it without much of a hassle, and the performance seems to be on par. I did encounter a bug, but the dev was quick to fix it. Just wanted to give them a shout-out.
Not a very good argument since vertical tabs take 10-12 cm of space, while regular horizontal ones take less than 2 cm.