Tab completion issue about fuzzyautocompleteplugin HOT 19 CLOSED

What's the reason behind wanting this feature? Is there a case where using normal completion is better?

from fuzzyautocompleteplugin.

I second this so I'll add my input as to why. I use the tab partial completion so heavily to narrow down my search results when i'm attempting to remember what the method/enum is I'm trying to actually complete. Having the tab partial completion is nice because it narrows down the list of possibles without me having to type so much.

Its not so much that is better but that it just makes the list smaller. Recent example I guess would be searching through UIFont stuff looking for UIFontDescriptorTrait enum and UIFontTextStyle enum and not remembering the prefixes 100%. The tab partial completion helps a lot in those kinds of cases.

from fuzzyautocompleteplugin.

So it's more when you're not sure what you're looking for? As of 1.3, you
can fuzzy match without needing to know the prefix.

On Tuesday, November 5, 2013, Daniel Miedema wrote:

I second this so I'll add my input as to why. I use the tab partial
completion so heavily to narrow down my search results when i'm attempting
to remember what the method/enum is I'm trying to actually complete. Having
the tab partial completion is nice because it narrows down the list of
possibles without me having to type so much.

Its not so much that is better but that it just makes the list smaller.
Recent example I guess would be searching through UIFont stuff looking
for UIFontDescriptorTrait enum and UIFontTextStyle enum and not
remembering the prefixes 100%. The tab partial completion helps a lot in
those kinds of cases.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-27756389
.

from fuzzyautocompleteplugin.

Partially I guess, that'd be one way to put it. I use the tab complete to shrink the autosuggest list just so I can read through my options easier. Sometimes I'm not sure what I want, other times I just want a short list of my options without having to type and just want to tab complete the beginning.

Probably a terrible example but having it override the default functionality of the tab key was a little jarring.

That's just how I use it and my input, I'm not sure how @Kapeli is using it specifically. I guess I'm just trying to say, I agree with the issue and would love to be able to use the default tab-parital completion along with this plugin since it makes the autocomplete awesome..

from fuzzyautocompleteplugin.

It's definitely not a huge issue.

My main reason is that I sometimes can't wrap my head around the new fuzzy completion and I'd just want to do it the old way. This usually happens when I'm in a hurry to type something large and I forget I have this fancy new plugin. So I guess this is something that might be considered to ease the transition for users that have not gotten used with fuzzy completion and have their brains hardwired on regular completion.

On the other hand, I can't think of one single case where fuzzy couldn't be used to achieve the same result (with less keystrokes). The issue is mostly that I forget fuzzy is there.

So it's up to you. It seemed like an easy fix to me and thought I should mention it. My brain will get used to fuzzy eventually.

from fuzzyautocompleteplugin.

👍 with @Kapeli ~
I have same behavior, too. But I will get used to fuzzy eventually.

from fuzzyautocompleteplugin.

I understand where you guys are coming from as transitionary features are
handy, but I can't think of a way where it will help you transition to
using fuzzy search more often.

Technically, it wouldn't be very hard to implement, but I just don't think
it would be a useful feature as is.

A useful indicator that fuzzy is available would be nice. Maybe it could
display a fuzzy search query that would result in the current top match
every time? I can see that being slow to compute though.

On Wednesday, November 6, 2013, Nelson wrote:

[image: 👍] with @Kapeli https://github.com/Kapeli ~
I have same behavior, too. But I will get used to fuzzy eventually.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-27786335
.

from fuzzyautocompleteplugin.

For me, it's not about making me use fuzzy more often. It's about avoiding frustration for those moments when I'm in a hurry and I don't have my mind set on fuzzy searching and I just do mechanically what I'm used to do.

At those moments, I know that fuzzy is available but I can't be bothered to use it, I just want to do what I'm used to and get over with with that line of repetitive code.

from fuzzyautocompleteplugin.

Hmm, fair enough.

You should be able to access the current filter prefix via _filteringPrefix instance variable and get the current highlighted match via self.selectedCompletionIndex and self.filteredCompletionsAlpha if you’re still interested in patching it yourself.

On Wednesday, 6 November 2013 at 8:45 am, Bogdan Popescu wrote:

For me, it's not about making me use fuzzy more often. It's about avoiding frustration for those moments when I'm in a hurry and I don't have my mind set on fuzzy searching and I just do mechanically what I'm used to do.
At those moments, I know that fuzzy is available but I can't be bothered to use it, I just want to do what I'm used to and get over with with that line of repetitive code.

—
Reply to this email directly or view it on GitHub (#12 (comment)).

from fuzzyautocompleteplugin.

That said, I think people would like it to be an option and I haven’t figured out a good way to manage options at this point.

On Wednesday, 6 November 2013 at 8:45 am, Bogdan Popescu wrote:

For me, it's not about making me use fuzzy more often. It's about avoiding frustration for those moments when I'm in a hurry and I don't have my mind set on fuzzy searching and I just do mechanically what I'm used to do.
At those moments, I know that fuzzy is available but I can't be bothered to use it, I just want to do what I'm used to and get over with with that line of repetitive code.

—
Reply to this email directly or view it on GitHub (#12 (comment)).

from fuzzyautocompleteplugin.

Let's keep this issue open for a while and see if there's anyone against having tab working as before.

from fuzzyautocompleteplugin.

I know there was at least one or two people that I talked to on IRC which requested that Tab inserting the current completion because it didn’t make sense for it to insert the prefix as it didn’t work/make sense with fuzzy.

On Wednesday, 6 November 2013 at 10:33 am, Bogdan Popescu wrote:

Let's keep this issue open for a while and see if there's anyone against having tab working as before.

—
Reply to this email directly or view it on GitHub (#12 (comment)).

from fuzzyautocompleteplugin.

Just to make it clear: the change I'm suggesting will only insert the prefix if you're NOT using fuzzy (i.e. you reach your autocompletion the regular way, by typing the prefix).

from fuzzyautocompleteplugin.

Yeah, I understand. I was just saying why I implemented the autocomplete on Tab in the first place.

On Wednesday, 6 November 2013 at 10:38 am, Bogdan Popescu wrote:

Just to make it clear: the change I'm suggesting will only insert the prefix if you're NOT using fuzzy (i.e. you reach your autocompletion the regular way, by typing the prefix).

—
Reply to this email directly or view it on GitHub (#12 (comment)).

from fuzzyautocompleteplugin.

Is this still an issue?

from fuzzyautocompleteplugin.

Hmm, was it ever fixed by a commit?

Just tried again.

Example with plugin on:

• I type NSMu and I get the top autocomplete result of NSMutableArray
• I press Tab
• NSMutableArray gets filled in, just like if I pressed Enter

Example with plugin off:

• Just like above, except that when I press Tab I get NSMutable filled in and I get to keep typing.

from fuzzyautocompleteplugin.

Nope, was just wondering if you got used to it yet :) So you want the old autocomplete behaviour when press tab? I might make that an optional feature.

from fuzzyautocompleteplugin.

Yep, I'd like that but only when what I've typed so far is the prefix of the current autocomplete result.

Unfortunately I'm not using Fuzzy Autocomplete due to other issues. I'll try to open some other issues when I've got some time. I might have gotten used to it if I actually used it, but I can't say for sure.

from fuzzyautocompleteplugin.

I had a crack at implementing this. I had the prefix inserting working fine, but when you press Tab to insert, it can give weird behaviour, so I made it an option.

from fuzzyautocompleteplugin.