[BUG] Rofi prefers recent over exact, even when both are recent

[codefaux]

Rofi version (rofi -v)

1.7.5

Configuration

https://gist.github.com/codefaux/6b772f2fd749d1fcace67cea9ebb5e7f

Theme

https://gist.github.com/codefaux/2fdd61da2c7be27e06d4d6dcdbec56a7

Timing report

No response

Launch command

rofi -show run

Step to reproduce

• have both st and steam installed
• rofi -show run
• type 'st'

Expected behavior

• have both st and steam installed
• rofi -show run
• type 'st'
• know that 'st' will be run every time, even if 'steam' and other commands beginning with 'st' exist

Actual behavior

• have both st and steam installed
• rofi -show run
• type 'st'
• observe that often 'steam' will sometimes be preferred over 'st' even if 'st' is a very recent run

Additional information

I feel like users should expect exact matches to be preferred over loose matches, or at least that a user expecting an exact match to be respected should have said expectation honored.

If it feels 'breaking' to change behavior as such, perhaps add a -prefer-exact argument?

Using wayland display server protocol

• No, I don't use the wayland display server protocol

I've checked if the issue exists in the latest stable release

• Yes, I have checked the problem exists in the latest stable version

[DaveDavenport]

Have you tried enabling sorting and setting matching algorithm? The provided config has it turned off.

I am not sure how this is a bug? it feels more like either misconfiguration or a feature request?

rofi -show run  -sort -sorting-method fzf

for me prefers st over steam even when steam has a higher 'count' in the run-cache.

[DaveDavenport]

Please open discussion on more questions, or a feature request if needed.

[DaveDavenport]

Here steam is used many times more then st.

[codefaux]

You're right, of course. My understanding was lacking, apologies for the wasted time. I did some searching and got incorrect information. I'm unfamiliar with the Github Discussions feature, I'll educate myself for the future.

Thank you.

[DaveDavenport]

No problem.

The discussion forum is linked in the template of the issue:

If you are unsure, please use the
discussion forum
first. It is easy to upgrade a question to an issue in github.