Mercurial > vim
comparison runtime/doc/eval.txt @ 13923:e4d5726e1678 v8.0.1832
patch 8.0.1832: cannot use :unlet for an environment variable
commit https://github.com/vim/vim/commit/137374fd6538cf9dee0cb22907728d8fdecb5832
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun May 13 15:59:50 2018 +0200
patch 8.0.1832: cannot use :unlet for an environment variable
Problem: Cannot use :unlet for an environment variable.
Solution: Make it work. Use unsetenv() if available. (Ken Takata,
closes #2855)
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Sun, 13 May 2018 16:00:07 +0200 |
| parents | 98274127d675 |
| children | cd513458728c |
comparison
equal
deleted
inserted
replaced
| 13922:1a30d378b70b | 13923:e4d5726e1678 |
|---|---|
| 9937 variables and script-local variables (these are not | 9937 variables and script-local variables (these are not |
| 9938 deleted when the script ends). Function-local | 9938 deleted when the script ends). Function-local |
| 9939 variables are automatically deleted when the function | 9939 variables are automatically deleted when the function |
| 9940 ends. | 9940 ends. |
| 9941 | 9941 |
| 9942 :unl[et] ${env-name} ... *:unlet-environment* *:unlet-$* | |
| 9943 Remove environment variable {env-name}. | |
| 9944 Can mix {name} and ${env-name} in one :unlet command. | |
| 9945 No error message is given for a non-existing | |
| 9946 variable, also without !. | |
| 9947 If the system does not support deleting an environment | |
| 9948 variable, it is made emtpy. | |
| 9949 | |
| 9942 :lockv[ar][!] [depth] {name} ... *:lockvar* *:lockv* | 9950 :lockv[ar][!] [depth] {name} ... *:lockvar* *:lockv* |
| 9943 Lock the internal variable {name}. Locking means that | 9951 Lock the internal variable {name}. Locking means that |
| 9944 it can no longer be changed (until it is unlocked). | 9952 it can no longer be changed (until it is unlocked). |
| 9945 A locked variable can be deleted: > | 9953 A locked variable can be deleted: > |
| 9946 :lockvar v | 9954 :lockvar v |