-
Notifications
You must be signed in to change notification settings - Fork 24
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
CTRL+D conflicts with Find and Replace settings ? #54
Comments
Open the search panel, select "Whole word search" (alt+w). Ctrl+D is affected by the selected search options, including whole word search and case sensitivity. |
Mmh, I cannot repro that, If I toggle "Whole word search", it does not change anything,
"sel" from "self" Is still selected. |
... You're right, I overinterpreted. I knew for a fact that case sensitivity affected the word matches but it seems the whole word match does not. A possibility to make it work however (which I just found "by accident") was to only place your cursor in the word I also seem to remember that there were differences in behavior whether the word was selected or not, but I'm not sure if that only applies to |
No selection! weird! Thanks for the tip |
I'm not sure, but seems to me that CTRL+D conflicts with Find and Replace settings, then I added to this package an option to mimic CTRL+D behaviour.. The thing is that the word highlighted by this package is in almost all the situations the word that I want to select. But since Find and Replace settings(or something else??), conflicts, it also select /portions/ of words and not complete words. CTRL+D ends hindering the selection.. so here we go..
In my setup CTRL+D with "sel" selected. Highlights
sel
= [s for s insel
f.view.sel
()]With this package now..
sel
= [s for s in self.view.sel
()]The explanation of how to add CTRL+D, CTRL+D + CTRL+K de6f919
The relevant portion 0035911
...........
The question is now, should we replace the standard keymaps?
invited, @facelessuser , @FichteFoll , @iamntz
The text was updated successfully, but these errors were encountered: