New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Supporting introspecting $E: as if it were a normal namespace #1026
Comments
Treating the |
Regarding the |
The Also as for the immediately preceding comment, But still, I agree that it could be handy to have |
Thanks, @hanche, as I had overlooked the |
I was too lazy to implement introspection operations on FWIW, namespaces and maps are distinct types in Elvish. Namespaces are reference types with a fixed set of keys while maps are value types. |
I was converting my fish functions for modifying my Anaconda virtual environment and was surprised to find I could not do
keys $E:
orhas-key $E: MY-ENV-VAR
. Is there some other way to iterate over, or test for the existence of a key, in that namespace? Note that relying on$E:vname
expanding to an empty string is not the same thing as knowing if the env var is set, even if set to the empty string.The text was updated successfully, but these errors were encountered: