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.
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.
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)
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.
There is a newish “placeholder text” option. It could be displayed there and disappear when typing starts.
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:
(ping @[email protected] )
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
Thanks! I’ll give this a try.
I’ll still get around to opening up an issue