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
I'm not in the practice of requesting features, but I feel this is one that is missing. It seems that un-setting a variable can be more difficult than it really should be, requiring a number of logic checks to ensure a setting is really gone. Could we have a:
set --ERASE foo
wherein, it actually un-sets the variable, regardless of scoping? I will even submit a pull request, if you agree. :-)
Thanks.
Additional details:
fish --version
fish, version 3.1.2
Ubuntu, Groovy
uname -a
Linux xxxxxxxx 5.8.0-7642-generic #47161228899020.10b8113e7dev-Ubuntu SMP Wed Feb 3 01:55:26 U x86_64 x86_64 x86_64 GNU/Linux
echo $TERM
xterm-256color
The text was updated successfully, but these errors were encountered:
Hello!
I'm not in the practice of requesting features, but I feel this is one that is missing. It seems that un-setting a variable can be more difficult than it really should be, requiring a number of logic checks to ensure a setting is really gone. Could we have a:
wherein, it actually un-sets the variable, regardless of scoping? I will even submit a pull request, if you agree. :-)
Thanks.
Additional details:
fish --version
fish, version 3.1.2
Ubuntu, Groovy
uname -a
Linux xxxxxxxx 5.8.0-7642-generic #47
161228899020.10b8113e7dev-Ubuntu SMP Wed Feb 3 01:55:26 U x86_64 x86_64 x86_64 GNU/Linuxecho $TERM
xterm-256color
The text was updated successfully, but these errors were encountered: