Lead dev of:
- https://github.com/nvim-neorocks/rocks
- https://github.com/nvim-neorg/neorg
For reasons to support us be sure to check out
beta.luanox.org/donate :D
For reasons to support us be sure to check out
beta.luanox.org/donate :D
You could throw a lua lib like github.com/kikito/i18n.... in your project and make a more accessible plugin than ever before 🎉
You could throw a lua lib like github.com/kikito/i18n.... in your project and make a more accessible plugin than ever before 🎉
I'll be releasing the page for beta testing to the public soon. It'll be a big test for the OAuth flow and key generation code :D
I'll be releasing the page for beta testing to the public soon. It'll be a big test for the OAuth flow and key generation code :D
This one will definitely need further touch-ups before the final release, but I'm happy with it as is for now :)
Next up, the page that generates API keys 🚀
This one will definitely need further touch-ups before the final release, but I'm happy with it as is for now :)
Next up, the page that generates API keys 🚀
github.com/neovim/neovi...
github.com/neovim/neovi...
I'm already done with the backend endpoints, which are much more convenient to use over luarocks.org, and they sure as hell don't encode the API key in the URL itself ☠️
I guess the next natural step is to create a "legacy" API which is luarocks-compatible
I'm already done with the backend endpoints, which are much more convenient to use over luarocks.org, and they sure as hell don't encode the API key in the URL itself ☠️
I guess the next natural step is to create a "legacy" API which is luarocks-compatible
Things left:
- Ask the user for email if OAuth didn't provide it
- Search functionality
- Package view page
- Plenty of touchups and more API endpoints
Exciting stuff ahead 🚀
Things left:
- Ask the user for email if OAuth didn't provide it
- Search functionality
- Package view page
- Plenty of touchups and more API endpoints
Exciting stuff ahead 🚀
We've had quite a few run-ins with the site misbehaving (as well as being slow) and so we're working on a sister site that will work in tandem with the main luarocks site :)
We've had quite a few run-ins with the site misbehaving (as well as being slow) and so we're working on a sister site that will work in tandem with the main luarocks site :)
It's high time that I return to writing some open source :)
It's high time that I return to writing some open source :)
I've been all about the stability for the past 9 months but I think it's time to move over to the unstable world for a bit again :)
Hoping this will rekindle my passion for Neovim as well as give me a playing field for the upcoming lux.nvim
I've been all about the stability for the past 9 months but I think it's time to move over to the unstable world for a bit again :)
Hoping this will rekindle my passion for Neovim as well as give me a playing field for the upcoming lux.nvim
- Minibuffers (many smaller buffers in a big buffer)
- Keybind namespaces (to allow overriding of all of Neovim's keybinds)
- Native luarocks support
- Minibuffers (many smaller buffers in a big buffer)
- Keybind namespaces (to allow overriding of all of Neovim's keybinds)
- Native luarocks support
I'll try to fill up a backlog of videos tomorrow, edit them in the following days, and go from there! I would also like to become a sort of news source for things going on in Neovim.
I'll try to fill up a backlog of videos tomorrow, edit them in the following days, and go from there! I would also like to become a sort of news source for things going on in Neovim.