Lines Matching refs:where

61 			where the map command applies.  The result, including
80 			where the map command applies.  Disallow mapping of
96 			Remove the mapping of {lhs} for the modes where the
98 			for other modes where it applies.
115 			Remove ALL mappings for the modes where the map
132 			List all key mappings for the modes where the map
148 			with {lhs} in the modes where the map command applies.
421 that quite often "Visual" is mentioned where both Visual and Select mode
536 When 'verbose' is non-zero, listing a key map will also display where it was
564 3. Use the termcap entry, with the form <t_xx>, where "xx" is the name of the
795 There are situations where key codes might not be recognized:
907 Xterm and a few other terminals can be put in a mode where keys with modifiers
961 			only result from Visual mode where "g@" is not useful.
1071 full-id	  In front of the match is a non-keyword character, or this is where
1079 	  or this is where the line or insertion starts.
1084 Examples: ({CURSOR} is where you type a non-keyword character) >
1134 			column indicates the mode where the abbreviation is
1140 When 'verbose' is non-zero, listing an abbreviation will also display where it
1285 In case the value is used in a context where <SID> cannot be correctly
1362 When 'verbose' is non-zero, listing a command will also display where it was
1425 "s:var" will use the script-local variable in the script where the command was
1426 defined, not where it is invoked!  Example:
1586 	-keepscript Do not use the location of where the user command was
1587 		    defined for verbose messages, use the location of where
1609 functions cannot be used.  Commands where a "|" may appear in the argument,
1745 script.  Thus this depends on where the command is defined, not where it is