@amiralies thank you! @ryyppy actually, from past experience, I think we’d instead like to fully control the editor experience so that we aren’t at the mercy of an independent release schedule (though this affects vim less). @amiralies is it ok if we copy this repo into the official rescript-lang org for now? We’d control it but it’s easier to loosen up than tightening; can always move this elsewhere later.
@amiralies actually I’ve changed my mind. I’m not sure we’ll be personally keeping the vim plugin well-maintained, so we can just make a note that it’s supported by a third party and direct to your repo. Then you can maintain it at your own pace.
The rationale was that there were occasions where disgruntled ex-contributors would sabotage a repo (not saying you would!), and an editor plugin is kinda important. But I’d like to default to good intention here. And the upfront notice of the plugin being unofficial should be enough for now.
Hello, I am having trouble setting up neovim to support rescript development. I added @amiralies vim script to my init.vim, and it is reading the filetype on load, but the syntax highlighting is not working automatically in .res files. I have to source my init.vim file in order for it to highlight the syntax. Thoughts?