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

Add pref to make multi-caret word insensitive #1131

Closed
Naatan opened this Issue Mar 4, 2016 · 11 comments

Comments

Projects
None yet
4 participants
@Naatan
Member

Naatan commented Mar 4, 2016

Suggested pref:

  • [checkbox] Make multi-caret word-insensitive if selection is longer than [textbox] characters

@Naatan Naatan added this to the 10.0 milestone Mar 4, 2016

@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Mar 11, 2016

Under what context/circumstances would this apply? Ctrl+D?

@Naatan

This comment has been minimized.

Member

Naatan commented Mar 12, 2016

Exactly, CTRL+D

@Naatan Naatan modified the milestones: 10.0, 10.1 Apr 28, 2016

@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Jun 16, 2016

Forgive my nitpickiness, but is this really useful? I cannot think of a case that would justify the work and pollution of the preferences page.

@Naatan

This comment has been minimized.

Member

Naatan commented Jun 16, 2016

I often find myself using Ctrl+D and it giving me mixed results. I don't have an explicit use-case right now that I can share, but it is something I find myself often running into.

How much work would be involved? I agree this likely does not merit a ton of time investment, but if it's only an hour or so I think it's worth it.

@cgchoffman

This comment has been minimized.

Member

cgchoffman commented Jun 16, 2016

I use Ctrl+D all the time but I don't understand what this is asking for otherwise I would weigh in.

@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Jun 20, 2016

@cgchoffman it sounds like if you Ctrl+D on something long like "foobarbaz", then instead of restricting multiple subsequent selections to "foobarbaz", it will select "fooBarBaz", "FOOBARBAZ", etc. (ignoring case). That's assuming the number of characters in "foobarbaz" is more than the one in the preference.

@Naatan yes, this would not take too long, but I still don't see a valid use case for this.

@Naatan

This comment has been minimized.

Member

Naatan commented Jun 20, 2016

Sorry, as said I don't currently have an explicit use-case, other than the fact that I have ran into it various times. We can leave this open until I run into it again so I can give a use case. If this is really fast to turn into a pref I prefer we just go ahead and do that though.

@Naatan

This comment has been minimized.

Member

Naatan commented Jun 29, 2016

Here's a use case:

        var emptyDirty = list.find("#staged-empty");
        if (stagedItems)
            emptyDirty.hide();
        else
            emptyDirty.show();

I want to change instances of "staged" to "empty". Currently multi-caret cannot help me with this as it considers staged-empty different from stagedItems (just the word "staged").

@Defman21

This comment has been minimized.

Contributor

Defman21 commented Jun 29, 2016

Good example! Sometimes I face with that as well.

@Naatan

This comment has been minimized.

Member

Naatan commented Jun 29, 2016

@mitchell-as perhaps rather than making this a pref we could simply add another command for it, which is word insensitive.

@mitchell-as

This comment has been minimized.

Member

mitchell-as commented Jun 29, 2016

I like that idea better with the separate command. The "longer than X characters" pref part is awkward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment