New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix slowness in Cursor.getCurrentWordBufferRange #15776

Merged
merged 6 commits into from Oct 1, 2017

Conversation

Projects
None yet
2 participants
@maxbrunsfeld
Contributor

maxbrunsfeld commented Sep 29, 2017

@leroix and I noticed this when doing some profiling atom/autocomplete-plus#886.

Uses atom/superstring#35

Show outdated Hide outdated src/cursor.js Outdated

maxbrunsfeld added some commits Oct 1, 2017

@maxbrunsfeld maxbrunsfeld merged commit 5a12c18 into master Oct 1, 2017

2 of 3 checks passed

continuous-integration/appveyor/pr Waiting for AppVeyor build to complete
Details
ci/circleci Your tests passed on CircleCI!
Details
continuous-integration/travis-ci/pr The Travis CI build passed
Details

@maxbrunsfeld maxbrunsfeld deleted the mb-optimize-word-under-cursor-search branch Oct 1, 2017

nathansobo added a commit that referenced this pull request Nov 2, 2017

Fix select-word command between word and non-word chararacters
In #15776, we accidentally stopped passing an option to the wordRegExp
method that caused us to prefer word characters when selecting words at
a boundary between word and non-word characters.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment