From 07fbdf4acc3b15ff97acb5c90243c61d938f8541 Mon Sep 17 00:00:00 2001 From: Jan Edmund Lazo Date: Mon, 1 Oct 2018 22:57:49 -0400 Subject: vim-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. (Yasuhiro Matsumoto, closes vim/vim#2855) https://github.com/vim/vim/commit/137374fd6538cf9dee0cb22907728d8fdecb5832 --- runtime/doc/eval.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'runtime') diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index 064c08c190..2e1d89c524 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -9136,6 +9136,14 @@ This does NOT work: > variables are automatically deleted when the function ends. +:unl[et] ${env-name} ... *:unlet-environment* *:unlet-$* + Remove environment variable {env-name}. + Can mix {name} and ${env-name} in one :unlet command. + No error message is given for a non-existing + variable, also without !. + If the system does not support deleting an environment + variable, it is made emtpy. + :lockv[ar][!] [depth] {name} ... *:lockvar* *:lockv* Lock the internal variable {name}. Locking means that it can no longer be changed (until it is unlocked). -- cgit