Hey Steven!
I'm not a user of vscode, but I'm trying to get to the bottom of a problem that may or may not involve this plugin... either way, it's a great first step in the search for a solution ;)
In the process of refreshing the csound manual, I noticed some of the example drafts @AsterixMusic was posting didn't compile when I tried. I tracked it down to this line:
ain1 diskin “fox.wav”, 1, 0
Which works fine if I delete the quote marks and retype them, so it now reads:
ain1 diskin "fox.wav", 1, 0
The first example Stefano created using an international layout keyboard, and is running them through vscode and this plugin to test (hence why I'm starting here).
I thought perhaps the editor itself is sanitizing the text before sending it to the api, so the plugin and csound itself has no idea the difference quotes ever existed! My other thought is that perhaps csound on the console behaves different than api, and I test on console whereas Stefano uses vscode and the plugin which I think is using api. But both of those are wild guesses, and I could be completely wrong.
Either way... just trying to figure out why this is happening, and whether or not a csound issue is relevant requesting that csound treat both style of quotes as the same (no idea if that has other implications tho).
Hey Steven!
I'm not a user of vscode, but I'm trying to get to the bottom of a problem that may or may not involve this plugin... either way, it's a great first step in the search for a solution ;)
In the process of refreshing the csound manual, I noticed some of the example drafts @AsterixMusic was posting didn't compile when I tried. I tracked it down to this line:
ain1 diskin “fox.wav”, 1, 0Which works fine if I delete the quote marks and retype them, so it now reads:
ain1 diskin "fox.wav", 1, 0The first example Stefano created using an international layout keyboard, and is running them through vscode and this plugin to test (hence why I'm starting here).
I thought perhaps the editor itself is sanitizing the text before sending it to the api, so the plugin and csound itself has no idea the difference quotes ever existed! My other thought is that perhaps csound on the console behaves different than api, and I test on console whereas Stefano uses vscode and the plugin which I think is using api. But both of those are wild guesses, and I could be completely wrong.
Either way... just trying to figure out why this is happening, and whether or not a csound issue is relevant requesting that csound treat both style of quotes as the same (no idea if that has other implications tho).