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

Menu search returns unrelated results [Regression] #8070

Closed
LingMan opened this issue Nov 26, 2018 · 8 comments
Closed

Menu search returns unrelated results [Regression] #8070

LingMan opened this issue Nov 26, 2018 · 8 comments

Comments

@LingMan
Copy link
Contributor

LingMan commented Nov 26, 2018

 * Cinnamon version: 4.0.1
 * Distribution: Manjaro
 * Graphics hardware *and* driver used: R9 390 with Kernel 4.18 and Mesa 18.2.5
 * 64 bit

Issue
Menu search lists unexpected items.

Steps to reproduce
Search for "cal".

Expected behaviour
The results are

  • Calculator
  • LibreOffice Calc
  • maybe other relevant elements

Actual behaviour
The results are

  • Calculator
  • Color
  • Date & Time
  • Hot Corners
  • LibreOffice Calc
    ...

Other information
This is a regression since Cinnamon 3.8. It feels like whatever fixed #4053 got removed again.

@Xeronel
Copy link

Xeronel commented Dec 1, 2018

I can confirm that I am also experiencing this issue. It is particularly bad for me when I type "ter" and get things like Skype, Online Accounts, Network, etc and my expected items like "Terminal" are way down at the bottom of all the unrelated items.

@Curly060
Copy link
Contributor

Curly060 commented Dec 3, 2018

I can confirm this, too. Commit a849090 is the culprit. That commit totally negates my original pull request #6929.
@clefebvre Could you please have a look at this? I know this search thing is a looong ongoing story, but now we are really back to square one.

@jarq6c
Copy link

jarq6c commented Dec 21, 2018

Just installed LM 19.1 and this problem persists. Search worked perfectly in 18.3. I expect to see Firefox and Firewall as the top search results if I type "f" or "fi", but this is not the case until "fir" is typed. If you type "f" or "fi", Archive Manager is the top search result.

@icarter09
Copy link
Member

icarter09 commented Dec 23, 2018

This issue is directly related to #8166, which explains why the search is actually returning correct results, but not in the intended affect that a search should work or how a user would anticipate the search to work.

@oles
Copy link

oles commented Jan 2, 2019

Cinnamon 4.0.8

screenshot from 2019-01-02 10-41-11

😕

Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 3, 2019
This commit tries to remedy the most pressing points
with the menu search for everyone. The changes are:
- by default only search in application names at word boundaries
- added a config switch to also search in keywords (keyword startsrWith)
- added a config switch to also search in description (at word
boundaries)
This is still not the desired behaviour, but certainly the best
compromise so far.
@Curly060
Copy link
Contributor

Curly060 commented Jan 3, 2019

I have made another attempt at fixing this. This is still not perfect, but hopefully it respects all wishes I have seen so far with the menu search:

  • by default the search only matches application names and only at word boundaries
  • added a config switch to also search in keywords (this is no longer a fulltext search on the keywords text but rather looks at each keyword in turn and if the keyword starts with the search pattern, that application is included)
  • added a config switch to also search in the description (only matches at word boundaries inside the description)

So there is no longer any kind of full text search in place any more at all. IMHO it makes no sense to find "starter" when you typed ter).

Because of the new settings the dialog currently isn't quite high enough. I don't know how to fix that.

I am well aware that this is still a workaround, but IMHO with compromises for everyone. Feel free to discuss this new approach. Any constructive feedback is welcome.

Cheers, Curly060 =;->

Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 3, 2019
This commit tries to remedy the most pressing points
with the menu search for everyone. The changes are:
- by default only search in application names at word boundaries
- added a config switch to also search in keywords (keyword startsrWith)
- added a config switch to also search in description (at word
boundaries)
This is still not the desired behaviour, but certainly the best
compromise so far.
@LingMan
Copy link
Contributor Author

LingMan commented Jan 4, 2019

After reading a few of the related tickets I think there are two distinct issues at play here.

First, the search often returns results which most people will consider unrelated, even when taking into account keywords and the description. These get returned because the old search matches at any place in the strings and not just at word boundaries. E.g. "Firefox" is found for the search term "ter" because it has the keyword "internet".
#6929 hid this because in most cases mentioned here a matching application was found. a849090 then made them visible again.

Second, even the expected search results are not sorted by their relevance. Introducing configuration options to enable or disable keyword and description searches can - at least in my opinion - only be a short term hack until #8166 gets fixed properly.
The question of weather the search results from keywords are wanted or not is dynamic and cannot be answered by a (relatively) static user setting.

Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 5, 2019
This is still a workaround until the whole search gets fixed completely.
The whole logic is now like this:
- search app names (at word boundaries) and also remember an eventual exact match
- if an exact match was found, stop searching
- if no exact match was found
-- search keywords (not as fulltext, each keyword in turn, at beginning of keyword)
-- search description (not as fulltext, but at word boundaries)

=> no more fulltext search at all
=> hopefully sensible results for everyone (as far as possible)
Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 5, 2019
This is still a workaround until the whole search gets fixed completely.
The whole logic is now like this:
- search app names (at word boundaries) and also remember an eventual exact match
- if an exact match was found, stop searching
- if no exact match was found
-- search keywords (not as fulltext, each keyword in turn, at beginning of keyword)
-- search description (not as fulltext, but at word boundaries)

=> no more fulltext search at all
=> hopefully sensible results for everyone (as far as possible)
@astier
Copy link

astier commented Jan 17, 2019

Yes this becomes really annoying. Often it is more efficient just to grab the mouse and select the desired result manually instead of typing the whole name of the desired application.

Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 28, 2019
This is still a workaround until the whole search gets fixed completely.
The whole logic is now like this:
- search app names (at word boundaries) and also remember an eventual exact match
- if an exact match was found, stop searching
- if no exact match was found
-- search keywords (not as fulltext, each keyword in turn, at beginning of keyword)
-- search description (not as fulltext, but at word boundaries)

=> no more fulltext search at all
=> hopefully sensible results for everyone (as far as possible)
Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 28, 2019
This is still a workaround until the whole search gets fixed completely.
The whole logic is now like this:
- search app names (at word boundaries) and also remember an eventual exact match
- if an exact match was found, stop searching
- if no exact match was found
-- search keywords (not as fulltext, each keyword in turn, at beginning of keyword)
-- search description (not as fulltext, but at word boundaries)

=> no more fulltext search at all
=> hopefully sensible results for everyone (as far as possible)
Curly060 pushed a commit to Curly060/Cinnamon that referenced this issue Jan 29, 2019
This is still a workaround until the whole search gets fixed completely.
The whole logic is now like this:
- search app names (at word boundaries) and also remember an eventual exact match
- if an exact match was found, stop searching
- if no exact match was found
-- search keywords (not as fulltext, each keyword in turn, at beginning of keyword)
-- search description (not as fulltext, but at word boundaries)

=> no more fulltext search at all
=> hopefully sensible results for everyone (as far as possible)
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

7 participants