Try to avoid using `lexer` as a string, as it overshadows the `lexer` module.

1 files changed, 6 insertions, 6 deletions

diff --git a/core/keys.lua b/core/keys.lua
index d805b4f1..59a2314f 100644
--- a/core/keys.lua
+++ b/core/keys.lua
@@ -10,12 +10,12 @@ local M = {}
 --
 -- Define key bindings in the global `keys` table in key-value pairs. Each pair
 -- consists of either a string key sequence and its associated command, a string
--- lexer language (from the *lexers/* directory) with a table of key sequences
--- and commands, a string key mode with a table of key sequences and commands,
--- or a key sequence with a table of more sequences and commands. The latter is
--- part of what is called a "key chain", to be discussed below. When searching
--- for a command to run based on a key sequence, Textadept considers key
--- bindings in the current key mode to have priority. If no key mode is active,
+-- lexer name (from the *lexers/* directory) with a table of key sequences and
+-- commands, a string key mode with a table of key sequences and commands, or a 
+-- key sequence with a table of more sequences and commands. The latter is part 
+-- of what is called a "key chain", to be discussed below. When searching for a 
+-- command to run based on a key sequence, Textadept considers key bindings in 
+-- the current key mode to have priority. If no key mode is active,
 -- language-specific key bindings have priority, followed by the ones in the
 -- global table. This means if there are two commands with the same key
 -- sequence, Textadept runs the language-specific one. However, if the command