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

markstos@lemmy.world · 2 months ago

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

jaxxed@lemmy.world · 2 months ago

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

jaxxed@lemmy.world · 2 months ago

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

markstos@lemmy.world · 2 months ago

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

jaxxed@lemmy.world · 2 months ago

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.

markstos@lemmy.world · 2 months ago

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

markstos@lemmy.world · 2 months ago

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

jaxxed@lemmy.world · 2 months ago

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.

markstos@lemmy.world · 2 months ago

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

jaxxed@lemmy.world · 2 months ago

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

jaxxed@lemmy.world · edit-2 1 month ago

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:

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 nobody@trickydicky.gov” 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)
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)
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