Add support for dashes as separators #16
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Julian
reviewed
Nov 17, 2018
| call search(join(left_boundaries, '\|'), 'bce') | ||
| let start_position = getpos('.') | ||
|
|
||
| let orig_iskeyword=&l:iskeyword |
There was a problem hiding this comment.
This looks suspicious to me.
I don't know that I'm thinking clearly enough, but I'd expect this to be done outside of this plugin entirely -- i.e., I'd expect this plugin to rely on a properly set iskeyword for the filetype that it's operating on, so if that ftplugin uses dashes, then we rely on that.
Perhaps you're doing this just to satisfy the test case you wrote (which by the way thanks!, well done on those)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Based on the work of @bkzl.