Page 1 of 1

Pref pane search feature can't handle a space

PostPosted: Tue May 05, 2020 7:03 pm
by dgbeecher
It seems that the search feature of the preference pane (ie, component #8 listed here) has trouble handling the space character. The search stops finding results as soon as I type any letter after a space.

For example, when searching "gas bill", the results go blank as soon as I type the "b" after the space.

And when searching "bank of america", the results go blank as soon as I type the "o" after the space.

This is particularly an issue for me because I handle paperwork for myself and my spouse. We have a lot of the same accounts, and I prepend rules for these accounts with our initials and a space. Because the space breaks the search, I can't effectively filter my rules to find each person's specific accounts.

If this has been reported before, my apologies; I searched but couldn't find anything similar.

If more information would be helpful, let me know and I'd be happy to provide.

Using Hazel 4.4.4 (build 1576) on macOS 10.15.4.

Re: Pref pane search feature can't handle a space

PostPosted: Wed May 06, 2020 9:21 am
by Mr_Noodle
I'll look into it though not sure when the next patch will go out.

Re: Pref pane search feature can't handle a space

PostPosted: Mon Nov 16, 2020 10:09 am
by dgbeecher
Hello Mr Noodle. Congrats on the release of v5! It looks very nice.

First thing I tested, of course, was whether the search feature could handle a space (as described above). Unfortunately, it seems it can't, yet.

I use the search feature all the time, and am always confused when it gives up on me after I type a space. Any chance this may be improved in the future?

Thank you ~~

Re: Pref pane search feature can't handle a space

PostPosted: Mon Nov 16, 2020 5:48 pm
by Mr_Noodle
Sorry I didn't get around to looking into this before. It's a bit lower priority compared other issues but I'll try and get to it at some point.

Re: Pref pane search feature can't handle a space

PostPosted: Tue Nov 17, 2020 12:21 am
by dgbeecher
:) Sounds good, thanks!