Fix up some punctuation/word boundary logic #6
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
bryan-codaio
force-pushed
the
bryan-punctuation
branch
3 times, most recently
from
e999cc2 to
dfc335a
Compare
bryan-codaio
force-pushed
the
bryan-punctuation
branch
from
dfc335a to
be02dff
Compare
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.
Changing the logic so characters like backticks, less than/greater than, etc. are treated as punctuation and thus as word boundaries, so that hitting opt+delete (on a mac) no longer kills my backticks.
I've cross-referenced this behavior with other editors such as vscode but also google docs.
I can't get
yarn installto work so my ability to progress on this is limited.