summaryrefslogtreecommitdiff
path: root/runtime/doc/usr_40.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2010-05-22 15:37:44 +0200
committerBram Moolenaar <Bram@vim.org>2010-05-22 15:37:44 +0200
commit06b5d5167a01c9fbf9661fb0c03bbd0a77cecae6 (patch)
tree4e4054360a178c58b1fb4e48bb51955f984a6b66 /runtime/doc/usr_40.txt
parentdb7c686ea58323f8e8550dea287eac7ea4964a55 (diff)
downloadvim-git-06b5d5167a01c9fbf9661fb0c03bbd0a77cecae6.tar.gz
Add the settabvar() and gettabvar() functions.
Various runtime file updates.
Diffstat (limited to 'runtime/doc/usr_40.txt')
-rw-r--r--runtime/doc/usr_40.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/runtime/doc/usr_40.txt b/runtime/doc/usr_40.txt
index 1aea1ac59..542a418c4 100644
--- a/runtime/doc/usr_40.txt
+++ b/runtime/doc/usr_40.txt
@@ -24,8 +24,8 @@ A simple mapping was explained in section |05.3|. The principle is that one
sequence of key strokes is translated into another sequence of key strokes.
This is a simple, yet powerful mechanism.
The simplest form is that one key is mapped to a sequence of keys. Since
-the function keys, except <F1>, have no predefined meaning in Vim, these are a
-good choice to map. Example: >
+the function keys, except <F1>, have no predefined meaning in Vim, these are
+good choices to map. Example: >
:map <F2> GoDate: <Esc>:read !date<CR>kJ