alda play --code misinterprets snippets with custom instrument names about alda

[daveyarwood]

This works for me in my Bash shell:

alda play -c 'piano "pi-1": c d e f g piano "pi-2":c < b a g f'

Based on this, it looks like you can use single quotes in PowerShell too. Can you try the snippet above?

I'm not sure why the version with the backticks wouldn't work as well, based on what I read in the article that I linked. 🤷‍♂️

[elydpg]

I tried the snippet above. Same problem

[daveyarwood]

I'm stumped. No idea why that wouldn't work, unless quoting works completely unexpectedly in PowerShell. 🤨

[elydpg]

Ok, where it gets even weirder is that Windows CMD (arguably a much "dumber" shell) has no problem with it, so long as you escape the quotes properly: alda play --code "piano \"pi-1\": c d e f g piano \"pi-2\": c < b a g f". However, running what you suggested in cmd tells me The system cannot find the file specified. And running alda play --code "piano "pi-1": c d e f g piano "pi-2": c < b a g f" gives me the same <no file>:1:1 undefined variable: piano error message I was seeing in PowerShell. I am honestly so confused...

[daveyarwood]

That error message makes "sense" to me in that that's the error message I would expect if you ran this:

alda play -c "piano " 

It seems like because of some Windows-specific shell quoting issues that I don't understand, it isn't actually escaping the first double quote after piano.

[daveyarwood]

And I have heard that single quotes don't work in CMD, for what it's worth.

[daveyarwood]

It seems clear to me that this is an issue with the way that quoting works in CMD and PowerShell, and not a bug in Alda, so closing this issue. Happy to reopen it if there are other perspectives!