summaryrefslogtreecommitdiff
path: root/runtime/doc/map.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2010-11-16 20:34:40 +0100
committerBram Moolenaar <Bram@vim.org>2010-11-16 20:34:40 +0100
commit166af9bb6f4f0c9a2f570766d26b42d2041860f2 (patch)
tree88791f76ef3946812ab212f61e130fdd39078852 /runtime/doc/map.txt
parent644d37b84d8f520f807ef665b476c47b72862eff (diff)
downloadvim-git-166af9bb6f4f0c9a2f570766d26b42d2041860f2.tar.gz
Updated runtime files.
Diffstat (limited to 'runtime/doc/map.txt')
-rw-r--r--runtime/doc/map.txt24
1 files changed, 14 insertions, 10 deletions
diff --git a/runtime/doc/map.txt b/runtime/doc/map.txt
index 055d33383..c18eed104 100644
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -1,4 +1,4 @@
-*map.txt* For Vim version 7.3. Last change: 2010 Sep 29
+*map.txt* For Vim version 7.3. Last change: 2010 Nov 10
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -1093,16 +1093,20 @@ is executed, it is transformed into a normal Ex command and then executed.
For starters: See section |40.2| in the user manual.
- *E183* *user-cmd-ambiguous*
+ *E183* *E841* *user-cmd-ambiguous*
All user defined commands must start with an uppercase letter, to avoid
-confusion with builtin commands. (There are a few builtin commands, notably
-:Next, :Print and :X, which do start with an uppercase letter. The builtin
-will always take precedence in these cases). The other characters of the user
-command can be uppercase letters, lowercase letters or digits. When using
-digits, note that other commands that take a numeric argument may become
-ambiguous. For example, the command ":Cc2" could be the user command ":Cc2"
-without an argument, or the command ":Cc" with argument "2". It is advised to
-put a space between the command name and the argument to avoid these problems.
+confusion with builtin commands. Exceptions are these builtin commands:
+ :Next
+ :X
+They cannot be used for a user defined command. ":Print" is also an existing
+command, but it is deprecated and can be overruled.
+
+The other characters of the user command can be uppercase letters, lowercase
+letters or digits. When using digits, note that other commands that take a
+numeric argument may become ambiguous. For example, the command ":Cc2" could
+be the user command ":Cc2" without an argument, or the command ":Cc" with
+argument "2". It is advised to put a space between the command name and the
+argument to avoid these problems.
When using a user-defined command, the command can be abbreviated. However, if
an abbreviation is not unique, an error will be issued. Furthermore, a