Bug 418541

Summary:	Actions show up in the application launcher
Product:	[Plasma] plasmashell	Reporter:	Rohde Fischer <rohdef>
Component:	Application Launcher (Kickoff) widget	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	kde, plasma-bugs-null
Priority:	NOR
Version First Reported In:	master
Target Milestone:	1.0
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Rohde Fischer 2020-03-06 12:36:23 UTC

This is becoming a huge pain in the a. Not sure why anyone would even want this feature (hint, when I'm opening the application launcher, I'm searching for - yes you guessed it: applications). However, at least have a way to disable this "feature", since it causes extreme amounts of noise.

STEPS TO REPRODUCE
1. Open the launcher
2. Type new
3. Pray that you don't have an application with a name beginning with new

OBSERVED RESULT
A huge amount of actions with names beginning with "new"


EXPECTED RESULT
Only applications


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 19.10

Comment 1 David Edmundson 2020-03-06 13:00:19 UTC

Please can you clarify what problem/inconvenience this causes. Applications should be weighted on top.

Comment 2 Kai Uwe Broulik 2020-03-06 13:08:17 UTC


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

Comment 3 Rohde Fischer 2020-03-06 13:40:21 UTC

(In reply to David Edmundson from comment #1)
> Please can you clarify what problem/inconvenience this causes. Applications
> should be weighted on top.

They aren't e.g. in the references bug in Spectacle, their "Capture XXX - Spectacle" actions turned up before Caprine. I ended up just removing Spectacle, to get rid the noise.

But that said, even if my applications were first... well I don't want the actions there, I don't want favorites from my browser, I don't want documents, I don't want the noise. Most of it I can disable, but for some reasons, I can't disable the actions

Comment 4 David Edmundson 2020-03-06 13:42:57 UTC

>They aren't

Ok, we can look into that.


>But that said, even if my applications were first... well I don't want the actions there

If you can justify it, it will be considered. "I don't want it" won't result in changes.

Comment 5 Rohde Fischer 2020-03-06 14:19:34 UTC

(In reply to David Edmundson from comment #4)
> >They aren't
> 
> Ok, we can look into that.
> 
> 
> >But that said, even if my applications were first... well I don't want the actions there
> 
> If you can justify it, it will be considered. "I don't want it" won't result
> in changes.

I would consider the simple argument of signal to noise ratio enough. But without access to statistics it's be hard to "justify". I have a hunch that this is one of those features most users don't use. But that I can't prove (nor disprove for that matter).

For the sake of it, I'm not even sure that matters. Likelihood is that if I'm wrong in my assumption I'm still not the only one bothered by this. If this is the case, wouldn't that by itself justify at least giving an option for this? Then the question would be if it's' enabled or disabled by default, which would probably be just a matter of statistics.