Skip to content
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

Open
titoBouzout opened this issue Jun 5, 2014 · 4 comments
Open

CTRL+D conflicts with Find and Replace settings ? #54

titoBouzout opened this issue Jun 5, 2014 · 4 comments

Comments

@titoBouzout
Copy link
Contributor

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 in self.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

@FichteFoll
Copy link
Member

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.

@titoBouzout
Copy link
Contributor Author

Mmh, I cannot repro that, If I toggle "Whole word search", it does not change anything,

sel = [s for s in self.view.sel()]

"sel" from "self" Is still selected.

@FichteFoll
Copy link
Member

... 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 sel (not select) it and press alt+f3. If you press it again (or have a word selected in general), you will get the same results as you outlined.

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 alt+f3 since it does not work with ctrl+shift+d.

@titoBouzout
Copy link
Contributor Author

No selection! weird! Thanks for the tip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants