summaryrefslogtreecommitdiff
path: root/runtime
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2017-02-20 22:35:33 +0100
committerBram Moolenaar <Bram@vim.org>2017-02-20 22:35:33 +0100
commite7877fe0de1426f8de9ada825e4f7b64810c7dbc (patch)
tree435e94a70fad5f665ff87c5470f2f4611c0e46c2 /runtime
parent673911457d6745b6b779eb769c2f41965592d12c (diff)
downloadvim-git-e7877fe0de1426f8de9ada825e4f7b64810c7dbc.tar.gz
patch 8.0.0343: b:changedtick can be unlockedv8.0.0343
Problem: b:changedtick can be unlocked, even though it has no effect. (Nikolai Pavlov) Solution: Add a check and error E940. (closes #1496)
Diffstat (limited to 'runtime')
-rw-r--r--runtime/doc/eval.txt7
1 files changed, 5 insertions, 2 deletions
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt
index bdc4b6388..30e71345a 100644
--- a/runtime/doc/eval.txt
+++ b/runtime/doc/eval.txt
@@ -9082,9 +9082,12 @@ This does NOT work: >
:lockvar v
:let v = 'asdf' " fails!
:unlet v
-< *E741*
+< *E741* *E940*
If you try to change a locked variable you get an
- error message: "E741: Value is locked: {name}"
+ error message: "E741: Value is locked: {name}".
+ If you try to lock or unlock a built-in variable you
+ get an error message: "E940: Cannot lock or unlock
+ variable {name}".
[depth] is relevant when locking a |List| or
|Dictionary|. It specifies how deep the locking goes: