Alfred List Filter Keyword Latching

[drgrib]

I can usually retrain Alfred with 2 or 3 manual selections after typing the letters I want it to match. For some reason, this isn't working with a list filter I have called "sitelinks". I type "si", press down to scroll through the results and manually select it, and press enter. It doesn't change in priority. Anything I can do to get Alfred to latch on to it for "si"?

 

 

Edited April 16, 2022 by drgrib
detail

[Chris Messina]

30 minutes ago, drgrib said:

For some reason, this isn't working with a list filter I have called "sitelinks".

 

Can you post a screenshot of the lower right corner of the list filter? Maybe you have this option set?

 

[drgrib]

I don't have it set, no. But that shouldn't matter for the primary list filter keyword "sitelinks" matching "si" right? That option should just be for the internal items once "sitelinks" has focus.

Edited April 16, 2022 by drgrib

[vitor]

Alfred won’t update the knowledge if you just autocomplete the List Filter’s keyword, you have to activate one of the options too.

[drgrib]

1 hour ago, vitor said:

Alfred won’t update the knowledge if you just autocomplete the List Filter’s keyword, you have to activate one of the options too.

 

I just tried selecting the first option in the "sitelinks" list 4 times and "sitelinks" still appears just as far down in the results for "si".

Edited April 18, 2022 by drgrib

[Andrew]

Confirmed by email that 4.6.6 b1300 fixes the behaviour, which was essentially a regression caused by this fix:

 

 

[drgrib]

@Andrew I think this bug has been reintroduced into Alfred 5. I'm noticing the same behavior with no latching for list filters again.

[Andrew]

Replied to @drgrib by email, but to help others:

 

The list filter argument needed to be set to Argument Optional, or Argument Required to get the latching working. Setting it to "No Argument" means that pressing return on the item is just autocompleting it, so it latches to the fully typed keyword instead.