diff options
author | Bram Moolenaar <Bram@vim.org> | 2019-06-14 14:39:51 +0200 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2019-06-14 14:39:51 +0200 |
commit | 37df9a4401f6737d6216306ea77a7e080c942aea (patch) | |
tree | 0a13846637d5b07c19a33432b36ffb386dd6d18b /runtime/doc/eval.txt | |
parent | b53fb31a1e27a806396e38592055cfb3ebf43cf9 (diff) | |
download | vim-git-37df9a4401f6737d6216306ea77a7e080c942aea.tar.gz |
patch 8.1.1526: no numerical value for the patchlevelv8.1.1526
Problem: No numerical value for the patchlevel.
Solution: Add v:versionlong.
Diffstat (limited to 'runtime/doc/eval.txt')
-rw-r--r-- | runtime/doc/eval.txt | 11 |
1 files changed, 11 insertions, 0 deletions
diff --git a/runtime/doc/eval.txt b/runtime/doc/eval.txt index 5f8156003..da45de805 100644 --- a/runtime/doc/eval.txt +++ b/runtime/doc/eval.txt @@ -2173,6 +2173,17 @@ v:version Version number of Vim: Major version number times 100 plus version 5.0 and 5.1 may have a patch 123, but these are completely different. + *v:versionlong* *versionlong-variable* +v:versionlong Like v:version, but also including the patchlevel. Version + 8.1 with patch 1234 has value 8011234. This can be used like + this: > + if v:versionlong >= 8011234 +< However, if there are gaps in the list of patches included + this will not work well. This can happen if a recent patch + was included into an older version, e.g. for a security fix. + Use the has() function to make sure the patch is actually + included. + *v:vim_did_enter* *vim_did_enter-variable* v:vim_did_enter Zero until most of startup is done. It is set to one just before |VimEnter| autocommands are triggered. |