dermusikman / sonicpi.vim Goto Github PK

Downloading an external version SuperCollider isn't required for Sonic Pi to work (it bundles it internally so the user does't have to bother installing it for their specific platform.

Hi @dermusikman!

I've been working on a fork of this sonicpi.vim plugin at https://github.com/lilyinstarlight/vim-sonic-pi. I'm wanting to start sharing my fork, but I noticed that there was no license in the original repository describing how the code can be used and modified.

Is my fork allowed and if so, are you able to license it under an open source license so that I can use it?

GitHub has a website at https://choosealicense.com/ for deciding on a license and while much of Sonic Pi is MIT licensed, I do not have a preference myself for which license you choose as long as it allows modification and distribution (which all of the licenses on that website allow).

Thank you for making sonicpi.vim and I hope you are safe and well!

Hello!

Is it possible to view error messages when a buffer is evaluated unsuccessfully due to an error?

Thanks,
Louis

I'm using neovim, and my used plugins and config can be found here: https://github.com/lpil/vimrc/blob/master/home/.vimrc

These commands should use the command variable.

So I write a simple play 70 buffer, execute !sonic_pi and then always get this error:

C:\WINDOWS\system32\cmd.exe /c (sonic_pi)
ERROR: Sonic Pi is not listening on 4557 - is it running?
shell returned 1
Hit any key to close this window...

I've checked, proccess are listening on correct ports. Tested with 4556 and 4558 as well.
Everything runs fine if I use sonic_pi GUI or open a cmd and run sonic_pi play 70

It looks like the file sonicpicomplete.vim was last updated more than 2 years ago.

Meanwhile, a few more synths and other options have been added to Sonic Pi, and it would be great to have them with the autocomplete feature of sonicpi.vim!

How is this file usually updated? By manually comparing with the Sonic Pi source code?

Otherwise, it could be interesting to automate this process, for example with a bunch of regular expressions on specific files to extract synth names, fx names and so on.

Also, the information about synths has been moved to: https://github.com/samaaron/sonic-pi/blob/master/app/server/sonicpi/lib/sonicpi/synths/synthinfo.rb

Hi there,

Thanks for creating this to make the Sonic Pi experience much much more awesome with vim - I'm wondering what should I do to be able to send a selected chunk of code to the sonic pi server, instead of the whole file I'm currently editing.

Thanks

Hi,
Thanks so much for this plugin - I really love it. One thing that I find annoying though is that changing buffers in vim sends the 'stop' command to sonic-pi. I have a 'utils' file with a heap of common functions, and I'll often want to work on them in one buffer while playing the 'main' buffer.

If you don't think this is a generally useful change, could you give me a hint about what I'd need to change in the vimscript to do it myself? I can't see anything obvious.

Cheers,

Ben