zlacker

Until you have to quote a string that has ampersands in it :)

>>haolez+(OP)
You mean like this...

' "Here is an ampersand... &" '

To clarify, in PowerShell there is a difference between text between single quotes (e.g. '$test') and double quotes (e.g. "$test"). Single quote strings are literal strings, so whatever text is contained within them is reproduced as written. Double quote strings are expandable strings, which means that certain text inside the string is evaluated before it is returned. If you have double quotes in a literal string, you'll see double quotes within that string, and the same should be true for ampersands.

>>haolez+(OP)
& has no special behaviour in strings, backticks and $ on the other hand do. For example "&Some String&" and '&Some String&' are all the literal value `&Some String&`. Backticks and $ are special in double quoted strings as they are the escape character and variable reference chars respectively.

>>ZenoAr+dF
That works in some cases, not others. I'm not saying that PowerShell is bad, but it certainly isn't a masterpiece of design.

>>haolez+8b6
What do you mean it works in some cases, not others? A literal string is a literal string in all cases.

As for it being a "masterpiece of design", it has it's quirks but compared to common Unix shells (aside from Nushell) it's far better. It doesn't need to have a perfect design in order to be a step above the competition.

I hope to continue to see the growth of Nushell, I can see that becoming the best shell one day.