Sort actions by usage

[emrroe]

When hitting alt, a list of alternative actions is shown. Most of the time however, the first option is the default action. It would be very useful if the last selected or most used option is moved to the top.
Aditionally hitting shift + enter could run this top alternative action

[schoettl]

I somehow like the idea of shift-enter for the alternative action.

Drawbacks are:

• it would be a hidden feature
• not clear what happens if there are more than two actions available

However, I'm not a fan of MRU logic for alternative actions. It adds complexity for a small benefit. And it's annoying when the order of the actions change from time to time. I would leave it to plugins to decide on the order of alternative actions - or they could make the order customizable.

[Redsandro]

I don't like things that change "automagically" because predictability makes usage intuitive and fast.

I would like checkbox options on the plugin settings page to indicate what option a specific user prefers to be default (#688), or some other way to make option order customizable as proposed by @schoettl.

Alternatively, @doktrjones' suggestion could be an option.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[cocoonkid]

This would be immensly useful!

[dreamcat4]

I don't like things that change "automagically" because predictability makes usage intuitive and fast

the actual reason for that is because albert 'hides' the actions list by default, and the currently selected action (default action) to be executed is (by default) written in really tiny font size beneath every single item. When compared to main text size.

So the current action is always either difficult to read, or getting towards impossible to read at any significant distance away from the screen, or if you have bad eyesight. So the stated problem is more coming about from bad UI, rather than a bad function / feature. Wouldn't you agree?

As always (since the very beginning of time), all these problems were solved pretty well in the original QuickSilver program for Mac. This was many years ago.

For an example of best practices, we can see here:

https://qsapp.com/wiki/Executing_actions

And really that solves the problem / reservation I quoted above ^^.

Of course we don't live in ideal world :) And with very limited resources. However you still have to acknowledge that Quicksilver was available on Mac since 20 years, on very old computers. So the performance they managed in the end was not usually the issue. More likely just a lot of very complex and clever coding. Which takes a lot of development time coding and struggles to get something robust and without spending a lot of time introducing new bugs etc.

[Iss-in]

can we please just have an extension setting to let user decide which preference he want , Not able to run commands in background by default is the sole reason I am unwillingly putting off its use since

[Asday]

My use case is I have executables that do things like mpv --shuffle --loop-playlist /mnt/192.168.1.2/Web\ Series/That\ Music/*.mkv, and it is never the case that I want a terminal. For cases where I do want a terminal, I will typically do kitty nano ~/filename.txt which has the added benefit of the terminal closing when the command completes.

I require no MRU logic or magic, I just want a switch somewhere that tells albert "ALWAYS run in the background for things prefixed with >".