Fuzzel, app launcher and fuzzy finder has feature-packed 1.11 release

markstos@lemmy.world to Linux@lemmy.ml – 120 points – Fuzzel, app launcher and fuzzy finder has feature-packed 1.11 release
mark.stosberg.com
21

How does its startup time compare to other launchers (rofi or tofi for example)

I never actually measured it, but I switched to fuzzel from wofi, and I can't tell the difference in reaction time. To me it feels instant.

I’ve tested them all and they all launch fairly immediately.

I discuss some of the other feature differences here:

https://mark.stosberg.com/rofi-alternatives-for-wayland/

I think for most people, Fuzzel will be the best choice, but compeitors offer unique features like Rofi-compatibility, HTML formatting support or the most important one: being written in Rust.

Love fuzzel—it’s pretty performant, even with a few thousand options to pick from.

Fuzzel is great. I only wish it had a pinentry option.

I should have read the article first -- passphrases and pinentry are here

That’s right! We are just waiting for someone to focus a pinentry/fuzzel script now. All the necessary features are there it seems.

The script is there in the post, but I haven't tried it yet. It would be nice if fuzzel had a message option, like rofi, so that key information could be displayed in the passphrases request; that s is what pinentry-rofi uses.

Yes. The message could be added to the prompt but it wouldn’t look the best.

It might be nice to have a way of giving more context, which is what the message option was good for in rofi. Not knocking it though, I am a happy fuzzel user.

You could add a feature request in the Fuzzel bug tracker. A screenshot of how it is used in Fuzzel could be helpful there.

Let me try for a pinentry script over the weekend first, to see how the placeholder looks.

Hey, sorry for taking a long time, but I am farting around with the pinentry option now.

I don't have screens, but I wanted to point out a few scenarios that are challenging with fuzzel:

  1. as I was trying to describe before, the ability to write accompanying text is pretty important, as you need to be able to describe what gpg key is to be unlocked, and typically a string like "Enter PIN for Richard Nixon " is used - which is too long for fuzzel (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-descriptive-text-to-display) Also keep in mind the error scenario, which adds even more copy (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-error-text). Lastly there is a "set window title" feature, which is perhaps not important for us (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-button-texts)
  2. There are message scenarios which are difficult to place with fuzzel. Even if I wanted to just fail out some scenarios like reties, I would want some "notification", and would probably like to have fuzzel also used for that in order to keep the UI consistend across use cases. (https://gorbe.io/posts/gnupg/pinentry/documentation/#message-box)
  3. There are cases where pinentry is expected to set copy for buttons for OK and Cancel and "Do not do this", IIRC to get internationalization. I think that these are less important. (https://gorbe.io/posts/gnupg/pinentry/documentation/#set-the-button-texts)

(ping @markstos@lemmy.world )

https://github.com/james-nesbitt/pinentry-fuzzel is a first try, shamelessly stealing everything from https://github.com/zamlz/pinentry-rofi/blob/main/src/pinentry-rofi.sh

There is a newish “placeholder text” option. It could be displayed there and disappear when typing starts.

I'm still on bemenu since I used dmenu with dwm on X. I should probably check the others out.

It looks like I have a great place to land if fzf ever starts to make my life difficult. Thank you!

fzf has some unique features of its own, like multi-select. Maybe one day Fuzzel will add that.