I wonder which IDE people are using for SuperCollider.
The Scide, Vim / Nvim, Emacs, VScode, something else and why? I prefer to use Emacs or Nvim (preference for Emacs, but not finally decided) as I’d like to use the same key bindings that I’m used to and Emacs has some nice goodies like the org mode which I have just discovered.
highly recommend Telescope and the Telescope plugin for SChelp
…recently though I’ve been enjoying using nvim-orgmode to organize many pieces of code and its made me think that emacs+orgmode+babel might be really a nice environment if you can tolerate emacs’ key-commands
I generated the assets, but I don’t know yet how to link to them in luasnip.lua.
I also asked in that thread:
My feeling is that there are so many plugins for nvim and many are not maintained anymore. Configuring emacs felt more straight forward. I completely got lost the overview when trying to configure nvim for SC. On the other hand lua is most likely easier to lean than elisp.
I did a little work in preparation to contribute an sclang lang module to Doom Emacs. Should make it easier for end-users to pick up without having to worry about configuration.
I was planning on supporting a +lsp flag to setup/wire-in the LSP server. Also grab the super collider tree-sitter grammar if that tool is active. Keybindings, not sure about those- I don’t think I’m the right person to set up those as I’m mostly interested in using Overtone (Clojure language front end to SuperCollider).
Not at present I was making one. Hadn’t touched in months though. Someone more savvy with Emacs & supercollider would certainly make a better one.
I have a private work-in-progress one at: ~/.config/doom/modules/lang/sclang/ containing packges.el, config.el, autoload.el just like other Doom modules. packages.el would load scel package, then if +lsp then … I didn’t get that far yet I think. Then add sclang to ~/.config/doom/init.el under lang comment to load it, should work.