I’m not sure why Travis should have failed...

Looks like unit tests

@muellmusik you have the ability to restart CI builds - login to Travis and AppVeyor with your github credentials (choose "SuperCollider" account in AppVeyor)

@brianlheim done in travis; can't see where to restart in AppVeyor. I was more wondering why a commit to an md file should cause builds to fail

Simple version of the answer - because our CI script sometimes fails for no good reason. Something to do with buffering.

Re AppVeyor if you follow the link from the failing build here and are signed into the supercollider acct you will see a "rebuild commit" button. Easy way to check kf you're signed into the right acct is by going to Projects and you should see sc and sc3 plugins as the projects available.

Re AppVeyor if you follow the link from the failing build here and are signed into the supercollider acct you will see a "rebuild commit" button. Easy way to check kf you're signed into the right acct is by going to Projects and you should see sc and sc3 plugins as the projects available.

I can see those, but can't see the rebuild button. Anyway, it's irrelevant for this PR, oder?

@brianlheim I tried again on my phone. Can see the projects, but not the rebuild button. It also says I can log in as you, which doesn’t seem right.

This is still failing on the Qt5.9 App Store build, but none of the changes touches compilable code, so I think it’s irrelevant. Is it possible to finish review and merge?

Yes, it's fine, the failure is just due to an old version of the appveyor script on your feature branch. Sorry that that noise was all over this PR. Also wanted to note that Core Team group members are definitely now able to restart AppVeyor builds; I had missed a checkbox within Appveyor's web UI. :) Thanks for your patience everyone!