There (finally) is a really great Lua Language Server implementation available at https://luals.github.io/, along with extensions for VSCode and NeoVim, which makes editing Lua in general a lot easier.
To make it usable with the Renoise API, I’ve started converting the old Renoise API definitions to the LuaCATS format and published them here:
I’m also planning to add some very basic auto-completion and typing information to Renoise to make it easier to write new scripts.
It would be great to make this a community effort, so contributions are welcome!
I once did something similar for vscode intellisense by scraping/reformatting the API docs. I am guessing this is the first step here too?
A lazy question to get a quick start and see if I understood it all:
Is this mainly for autocompletion, tooltips and possibly snippets eventually? The latter I would imagine to be quite powerful when learning the API.
EDIT: “LuaLS provides various features for Lua in code editors, such as autocompletion, type hovers, dynamic type checking, diagnostics and more”. It would be interesting to see what it can do in practice in addition to autocompletion/tooltips.
PS. I must say it would be a big leap to switch from the excellent native editor, given the issue with auto-reloading when editing ‘required’ files. But it might be worth it!
As far i understand it right it is a comment type definition system for supporting intellisense, code suggestion and automatik codecompletation for Renoise LUA Scripting enviroment in VSCode? Is this correct? And you need help defining these comment types for existing Renoise LUA Functions right?
Yes, i could help you, but i dont have a Github account. That why i cannot fork your project. but i could download it as zip, do the job and could you give the overworked files via Discord. Is that ok for you? If so we should speak about sharing work, thats none of the files workenend from us both same time.
Yes, exactly. Simply give it a try with the definitions which are already there renoise.app() in vscode.
I must say it would be a big leap to switch from the excellent native editor
I’ll try to integrate the most basic auto-complete and hover type info into the Renoise built in editor as well, but can’t promise anything here. We won’t be able to compete with vscode’s feature set, and actually should not even try to
Yes. Rewriting the old docs to use the LuaCATS annotations is quite some work. Probably someone could try to writie a script which semi-converts the old annotations to the new ones. This needs to be manually edited afterwards then anyway.
One more question here: If I update any other script (not main.lua), and then save main.lua again, without added changes to it, will the whole thing still reload after switching to Renoise GUI again?
I saw this when it was posted, and I began to wonder - is this how Renoise might get granular/wavetable functionality? Just askin’. Took another look, I’m probably just dreamin’.
@taktik Do you still need help mate? You dont react on my question. I cant fork your git repo because i dont have any Git Account anymore. But i could download the git repo and help converting the files and upload it to Discord for you?
We plan on including some native renoise granular and crossfading wavetable instruments in the next renoise release
To be clear, these will be utilizing the current capabilities of renoise - so it’s stuff we can already do now - but will allow for some nice sonic possibilities for renoise users without having to reinvent the wheel and do all the setup work
