After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 727341 - Searching for "+" doesn't match "Google+" application launcher
Searching for "+" doesn't match "Google+" application launcher
Status: RESOLVED DUPLICATE of bug 764417
Product: glib
Classification: Platform
Component: gio
unspecified
Other Linux
: Normal minor
: ---
Assigned To: gtkdev
gtkdev
Depends on:
Blocks:
 
 
Reported: 2014-03-30 12:25 UTC by António Fernandes
Modified: 2017-09-13 12:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description António Fernandes 2014-03-30 12:25:45 UTC
I installed Google+ as Web Application from epiphany. Given I already have another application whose name starts with "Google" (Google Chrome), I thought it would be easier to match "Google+" searching for "+". To my surprise it did not return any application launcher result.

   Steps to reproduce:

1. Launch epiphany and go to https://plus.google.com
2. Save as web application ( [Ctrl]+[Shift]+[A] )
3. Open activities overview
4. Type "+".

   Expected result:

Google+ application launcher is found.

   Actual result:

No application launcher is found.

(Epiphany search provider returns Google+, but that will open the page in a normal epiphany window, not the web application.)
Comment 1 Florian Müllner 2014-03-30 13:02:57 UTC
That's because g_desktop_app_info_search() doesn't do substring matches on words. Reassigning.
Comment 2 Allison Karlitskaya (desrt) 2014-03-30 13:15:55 UTC
Actually, it's because we don't do any searching at all on punctuation...
Comment 3 Philip Withnall 2017-09-13 12:06:26 UTC
With the aim of avoid two bugs competing over how to modify the heuristics for g_desktop_app_info_search(), let’s mark this as a duplicate of bug #764417. I’ll mention the potential need for including punctuation in the search there.

*** This bug has been marked as a duplicate of bug 764417 ***