@@ -162,7 +162,8 @@ allows snippets to be conveniently separated by a single blank line.
162
162
The `option ` s control the behavior of the expansion of the snippet and are
163
163
optional. Currently supported are the following:
164
164
- `w ` Word boundary - The word expands only when the trigger is on a word
165
- boundary. This is the default behavior.
165
+ boundary. A | word | in this context is a sequence of | iskeyword |
166
+ characters.
166
167
- `i ` In-word expansion - The snippet gets expanded even if the trigger is
167
168
only part of the word, up to the cursor.
168
169
- `b ` Beginning of line - The snippet is only expanded if its trigger is
@@ -172,9 +173,13 @@ optional. Currently supported are the following:
172
173
this feature, because it checks every key pressed, may theoretically
173
174
affect the performance of your editor when used.
174
175
175
- Custom `option ` s can be defined via the setup option `expand_options` to restrict
176
- expansion in specific scenarios. For example, consider latex snippets which
177
- should only be expanded when inside of a math environment or in comments:
176
+ Note that the default behavior is to only expand if the whole | WORD |
177
+ (space-delimited) before the cursor matches the trigger.
178
+
179
+ Custom `option ` s can be defined via the setup option `expand_options` to
180
+ restrict expansion in specific scenarios. For example, consider latex snippets
181
+ which should only be expanded when inside of a math environment or in
182
+ comments:
178
183
>lua
179
184
expand_options = {
180
185
m = function()
0 commit comments