#scnvim — Public Fediverse posts

Oh, #neovim has a new version. Let's see whether this fixes the odd bug I keep having with #scnvim.

Oh, #neovim has a new version. Let's see whether this fixes the odd bug I keep having with #scnvim.

Oh, #neovim has a new version. Let's see whether this fixes the odd bug I keep having with #scnvim.

Oh, #neovim has a new version. Let's see whether this fixes the odd bug I keep having with #scnvim.

I played around with one idea from my livestreams tonight, exploring fmgrains a bit. Next stop: messing around with Ugens that incorporate ambisonic panning.

I am so happy that I got #scnvim to work again - I really didn't know what i was missing and how productive working in neovim makes me feel!

#SuperCollider

I played around with one idea from my livestreams tonight, exploring fmgrains a bit. Next stop: messing around with Ugens that incorporate ambisonic panning.

I am so happy that I got #scnvim to work again - I really didn't know what i was missing and how productive working in neovim makes me feel!

#SuperCollider

I played around with one idea from my livestreams tonight, exploring fmgrains a bit. Next stop: messing around with Ugens that incorporate ambisonic panning.

I am so happy that I got #scnvim to work again - I really didn't know what i was missing and how productive working in neovim makes me feel!

#SuperCollider

I played around with one idea from my livestreams tonight, exploring fmgrains a bit. Next stop: messing around with Ugens that incorporate ambisonic panning.

I am so happy that I got #scnvim to work again - I really didn't know what i was missing and how productive working in neovim makes me feel!

#SuperCollider

Ouf. I finally got around to reporting the annoying bug that has kept me from using #scnvim ever since it transitioned to lua configuration:
https://github.com/davidgranstrom/scnvim/issues/209

Ouf. I finally got around to reporting the annoying bug that has kept me from using #scnvim ever since it transitioned to lua configuration:
https://github.com/davidgranstrom/scnvim/issues/209

Ouf. I finally got around to reporting the annoying bug that has kept me from using #scnvim ever since it transitioned to lua configuration:
https://github.com/davidgranstrom/scnvim/issues/209

Ouf. I finally got around to reporting the annoying bug that has kept me from using #scnvim ever since it transitioned to lua configuration:
https://github.com/davidgranstrom/scnvim/issues/209

@draco #scnvim changed my life! what platform are you on and what problem are you seeing?

@draco #scnvim changed my life! what platform are you on and what problem are you seeing?

@draco #scnvim changed my life! what platform are you on and what problem are you seeing?

I made another attempt at configuring #scnvim and got that same issue that stopped me earlier. All seems fine ... until I boot the server.

Will write about that more later.

#SuperCollider #neovim

I made another attempt at configuring #scnvim and got that same issue that stopped me earlier. All seems fine ... until I boot the server.

Will write about that more later.

#SuperCollider #neovim

I made another attempt at configuring #scnvim and got that same issue that stopped me earlier. All seems fine ... until I boot the server.

Will write about that more later.

#SuperCollider #neovim

Tried to update my #scnvim to a lua-based config, but now #neovim crashes as soon as I boot the #SuperCollider server, spitting out weird lua error messages. :(

Tried to update my #scnvim to a lua-based config, but now #neovim crashes as soon as I boot the #SuperCollider server, spitting out weird lua error messages. :(

Tried to update my #scnvim to a lua-based config, but now #neovim crashes as soon as I boot the #SuperCollider server, spitting out weird lua error messages. :(

Just found out that increment/decrement mapping is the default mapping in #neovim and perfect for working with #supercollider in #scnvim

http://bit-101.com/techtips/2018/02/23/Increment-Decrement-Numbers-in-vim/

Just found out that increment/decrement mapping is the default mapping in #neovim and perfect for working with #supercollider in #scnvim

http://bit-101.com/techtips/2018/02/23/Increment-Decrement-Numbers-in-vim/

Just found out that increment/decrement mapping is the default mapping in #neovim and perfect for working with #supercollider in #scnvim

http://bit-101.com/techtips/2018/02/23/Increment-Decrement-Numbers-in-vim/

For the past week or so, I have started seeing weird instabilities in #scnvim. It crashes whenever I use floating point numbers as an argument.

I have no idea if it's scnvim itself or if some other plugins conflict with scnvim.

It's stable when I use other languages.

I'm using the standard SuperCollider IDE for the time being, but I miss vim's functionalities.

For the past week or so, I have started seeing weird instabilities in #scnvim. It crashes whenever I use floating point numbers as an argument.

I have no idea if it's scnvim itself or if some other plugins conflict with scnvim.

It's stable when I use other languages.

I'm using the standard SuperCollider IDE for the time being, but I miss vim's functionalities.

For the past week or so, I have started seeing weird instabilities in #scnvim. It crashes whenever I use floating point numbers as an argument.

I have no idea if it's scnvim itself or if some other plugins conflict with scnvim.

It's stable when I use other languages.

I'm using the standard SuperCollider IDE for the time being, but I miss vim's functionalities.

In today's news: Going to bed too late because I'm trying to figure out why #scnvim refuses to boot the :sccube: server on Windows when I try to specify audio devices other than the default.

well... good night. Maybe I'll wake up with some insight.

In today's news: Going to bed too late because I'm trying to figure out why #scnvim refuses to boot the :sccube: server on Windows when I try to specify audio devices other than the default.

well... good night. Maybe I'll wake up with some insight.

My current setup:
OS: #archlinux with #swaywm
Music: #supercollider #scnvim #audacity
Video: #kdenlive
Terminal emulator: #termite
Editor: #neovim
Mail: #isync #notmuch #neomutt
Contacts: #khard
Calendar: #khal
Office: #libreoffice
System upgrade: #topgrade

Poking my little toes into the deep, deep waters of #emacs by way of #doom... Starting out with getting emacs working properly for me as an email client, in conjunction with notmuch and mbsync. So far I am very happy. I can piggyback on the setup I made years ago with neomutt. Once that nut is cracked I will start to nibble off other crackers. Org mode seems to be all the rage... and then getting #supercollider into as good a state as I have with #scnvim. and then... who knows?

Now I know why my custom #scnvim keymappings working yesterday... I had some typos in one line that I had copied 5 times.

That's easily fixed. Which is good because scnvims default mapping for evaluing a line or selection is kinda cramped in bone. Now I've mapped code execution to the default mappings from scide.

The sixth 'miniature'! The mixing is a bit off, but hey! What can one do?

I'd been having problems with #Supercollider, and in specific #scnvim. Basically, it just didn't work. It's most probably my neovim setup and I shall delve more deeply into that when I have time. I constructed a few hacks to get things working once again. Thus, this piece includes supercolliding. Thanks to @madskjeldgaard for help.

https://funkwhale.thurk.org/library/tracks/2198/

#music #psychedelic #ambient #AmbientGuitar #electronic

Maybe, at some point, I'll write a little blogpost about my adventure of getting #supercollider to work with #scnvim on my netbook.

OK, it turned out that sclang was not in my $PATH, and adding it did the trick!

#scnvim #troubleshooting #SuperCollider

I tried to get #scnvim working and I couldn't. It doesn't find sclang.exe because I can't figure out how to escape that one space in the file path; if I leave the variable in my .vimrc blank, it doesn't find it either.

Damn you, Windows. (I can't ditch it because of work, and I don't have the disk space for dual boot.)

I haven't tried commenting the line out entirely yet; maybe I'll try that tomorrow. But beyond that, I'm really stumped.

Is anyone here who uses #scnvim on Windows10? I keep getting weird error messages on startup (something along the lines of "Message 'globalKeyDown' not understood") and despite having specified the location of pandoc.exe in my .vimrc, it also gives me "C:\Program is misspelled or could not be found".

@kf

I use vim for my supercolliding, as well, and from time to time, I've investigated the things you've tooted about #scnvim. I am and have been intrigued, but not been pushed over the "precipice" yet, as my use of supercollider is far less involved than yours. But this lua thing has me thinking....

@flavigula I was pushed over the edge a couple of years ago by the very awesome #scnvim plug-in for #supercollider. The emergence of lua is a big bonus that I didn’t even know I wanted at the time :-)

Fiddled around with #scnvim today, and I got the server to boot and play some synths, but it is still throwing a lot of errors on Windows 10 at startup.

I cannot access the documentation within SCNvim at the moment; something must still be off with the configuration.

https://github.com/davidgranstrom/scnvim/pull/57

This is great news for the #scnvim breed of #supercollider peeps! Finally we get a bit of that Document breeze...

#introduction Hi all! I’m a Norwegian choreographer/composer/creative coder/producer (too many labels already...) living in Estonia, and working internationally together with my partner Külli Roosna. These days I’m mostly dealing with the body and its technological extensions. My main tools are #supercollider (#scnvim), #minibee accelerometers and all sorts of #foss software, running on #archlinux and #swaywm. Looking forward to getting to know you and this instance!

Poking my little toes into the deep, deep waters of #emacs by way of #doom... Starting out with getting emacs working properly for me as an email client, in conjunction with notmuch and mbsync. So far I am very happy. I can piggyback on the setup I made years ago with neomutt. Once that nut is cracked I will start to nibble off other crackers. Org mode seems to be all the rage... and then getting #supercollider into as good a state as I have with #scnvim. and then... who knows?

Now I know why my custom #scnvim keymappings working yesterday... I had some typos in one line that I had copied 5 times.

That's easily fixed. Which is good because scnvims default mapping for evaluing a line or selection is kinda cramped in bone. Now I've mapped code execution to the default mappings from scide.

The sixth 'miniature'! The mixing is a bit off, but hey! What can one do?

I'd been having problems with #Supercollider, and in specific #scnvim. Basically, it just didn't work. It's most probably my neovim setup and I shall delve more deeply into that when I have time. I constructed a few hacks to get things working once again. Thus, this piece includes supercolliding. Thanks to @madskjeldgaard for help.

https://funkwhale.thurk.org/library/tracks/2198/

#music #psychedelic #ambient #AmbientGuitar #electronic

Maybe, at some point, I'll write a little blogpost about my adventure of getting #supercollider to work with #scnvim on my netbook.