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
In bash a variable valuable can be accessed with the dollar sign $varname. That gets value of a local variable and fall backs to environment variable.
In closh it is currently done with (str varname) and (getenv "varname") which can become quite chatty. I am considering whether we should expand variable value with dollar sign too. Should we also fall back to environment variable?
With the fall back $varname could become something like:
Another thing is expansion in strings: "$a/${b}". Here are am leaning against it since it gets complicated with escaping rules.
Workaround can be to used some string interpolation library like strint/<< or cuerdas istr: (istr "~{a}/~{b}"). But maybe we could try to create a library to implement this in a bash compatible way like ($ "$a/${b}").
The text was updated successfully, but these errors were encountered:
In bash a variable valuable can be accessed with the dollar sign
$varname
. That gets value of a local variable and fall backs to environment variable.In closh it is currently done with
(str varname)
and(getenv "varname")
which can become quite chatty. I am considering whether we should expand variable value with dollar sign too. Should we also fall back to environment variable?With the fall back
$varname
could become something like:Another thing is expansion in strings:
"$a/${b}"
. Here are am leaning against it since it gets complicated with escaping rules.Workaround can be to used some string interpolation library like strint/<< or cuerdas istr:
(istr "~{a}/~{b}")
. But maybe we could try to create a library to implement this in a bash compatible way like($ "$a/${b}")
.The text was updated successfully, but these errors were encountered: