Re: Comment (# char) behavior in the sub-shell

[Stanislav Seletskiy <s.seletskiy@xxxxxxxxx>]

> I suspect this changed some versions ago now.  At some point we changed
> the way we handled $(...) to parse it better.  Previously, we just
> blindly treated it as a string when we first enountered it, reading it
> in interactively until we got to a closing parenthesis.  That wasn't
> actually the right thing to do, and crucially it failed where there was
> a case statement in the old syntax where a pattern only has a closing
> parenthesis and not an opening parenthesis.  So what we do now is parse
> properly until the (right) closing parenthesis, but still store what we
> parsed as a string for reading again when we execute the $(...).

So, shouldn't it be fixed? It's very misleading, since for me as for
user $(...) that I type in the shell is still interactive mode and
should be treated in the same way.