Mercurial > vim

diff runtime/doc/map.txt @ 30920:93b603c24d23 v9.0.0794

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
patch 9.0.0794: there is no way to find out if modifyOtherKeys has been seen Commit: https://github.com/vim/vim/commit/9f62ea01a08e69f44050f59469a0e64beddefac0 Author: Bram Moolenaar <Bram@vim.org> Date: Wed Oct 19 13:07:03 2022 +0100 patch 9.0.0794: there is no way to find out if modifyOtherKeys has been seen Problem: There is no way to find out if an escape sequence with modifyOtherKeys has been seen. Solution: Add a notice with ":verbose map".
author Bram Moolenaar <Bram@vim.org>
date Wed, 19 Oct 2022 14:15:03 +0200
parents 1e91e26ceebf
children eb2638f278bf
line wrap: on
line diff
--- a/runtime/doc/map.txt
+++ b/runtime/doc/map.txt
@@ -989,6 +989,11 @@ mapping, see |map-bar|.
 WARNING: if you map <C-[> you may very well break any key codes that start
 with Esc.  Make sure it comes AFTER other mappings.
 
+Vim automatically detects if the modifyOtherKeys mode was enabled when it
+spots an escape sequence that must have been created by it.  To see if Vim
+detected such an escape sequence use `:verbose map`, the first line will then
+show "Seen modifyOtherKeys: true" (possibly translated).
+
 A known side effect is that in Insert mode the raw escape sequence is inserted
 after the CTRL-V key.  This can be used to check whether modifyOtherKeys is
 enabled: In Insert mode type CTRL-SHIFT-V CTRL-V, if you get one byte then