fix: Correct taking content after cursor #88
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
|
@p12tic Sorry, this problem has been bothering me, is this fix okay for you? |
p12tic
approved these changes
Mar 4, 2025
|
Perhaps worth merging after #90 so that it's clear how behavior is changed. |
|
If you don't mind I can update tests for this PR as well |
Palm1r
force-pushed
the
fix-getting-content-after-cursor
branch
from
3bbbb2c to
5aaf3db
Compare
|
I looked into test failures and it seems this needs more work. |
|
@p12tic yeah, you can continue the PR |
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.
This fix solves the problem when the text after the cursor from the same line was not included in the query