Skip to content

Commit ab11ba0

Browse files
committed
revert: word options is now default
This reverts commit 318ab24.
1 parent c4f048b commit ab11ba0

File tree

1 file changed

+4
-9
lines changed

1 file changed

+4
-9
lines changed

doc/snippy.txt

+4-9
Original file line numberDiff line numberDiff line change
@@ -162,8 +162,7 @@ allows snippets to be conveniently separated by a single blank line.
162162
The `option`s control the behavior of the expansion of the snippet and are
163163
optional. Currently supported are the following:
164164
- `w` Word boundary - The word expands only when the trigger is on a word
165-
boundary. A |word| in this context is a sequence of |iskeyword|
166-
characters.
165+
boundary. This is the default behavior.
167166
- `i` In-word expansion - The snippet gets expanded even if the trigger is
168167
only part of the word, up to the cursor.
169168
- `b` Beginning of line - The snippet is only expanded if its trigger is
@@ -173,13 +172,9 @@ optional. Currently supported are the following:
173172
this feature, because it checks every key pressed, may theoretically
174173
affect the performance of your editor when used.
175174

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:
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:
183178
>lua
184179
expand_options = {
185180
m = function()

0 commit comments

Comments
 (0)