feat: add smartcase setting for jump-to-char#43
Closed
mtoohey31 wants to merge 1 commit into
Closed
Conversation
sxyazi
force-pushed
the
main
branch
2 times, most recently
from
93e0b4e to
6418698
Compare
sxyazi
force-pushed
the
main
branch
2 times, most recently
from
1ff5f8b to
4df8f70
Compare
Author
|
Closing as there are conflicts and I'm not using yazi right now. If someone else wants to fix this up and create a new PR they're welcome. |
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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 was my first draft. Some other things I considered were nesting the setup argument inside a table to make things more readable (i.e. the setup call would be
require("jump-to-char"):setup({ smart = true })), or supporting arbitrary additional arguments to the"find_do"emit. Let me know if either of those sound useful!Closes #35.