You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can kind of turn off variable interpolation by passing x => "$" + x for env, but not really, because then "${THING}" will get turned into "$THING" instead of remaining as "${THING}".
Also, it would be nice to have a way to turn off things like operator, comment, and glob handling as well, and just treat these as ordinary strings. (Glob handling isn't even documented at all, and so is a potential landmine for users who don't read the code...)
Thanks!
The text was updated successfully, but these errors were encountered:
I mean basically in our context what's going on is we have something that provides a shell-like interface for commands, but doesn't have anywhere near the power of a real shell, such that attempting to handle operators, etc, doesn't make sense, as we won't be able to do anything with them. But we want to make sure that the user can use quotes or backslashes to include spaces in things, etc.
You can kind of turn off variable interpolation by passing
x => "$" + x
forenv
, but not really, because then"${THING}"
will get turned into"$THING"
instead of remaining as"${THING}"
.Also, it would be nice to have a way to turn off things like operator, comment, and glob handling as well, and just treat these as ordinary strings. (Glob handling isn't even documented at all, and so is a potential landmine for users who don't read the code...)
Thanks!
The text was updated successfully, but these errors were encountered: