jaxxed

Can we just clarify that you mean that comments should never be parsed by the language engine. There are valid annotation systems, but the goal is alway to ensure that one passable can never impact the other.

Imagine if here a comment could create a syntax error! This is even worse for runtime scripting languages like python.

I have no problems with the action, and I have no problems with his attitude.

The effort to isolate Russia is an acceptable result of the Russian violent invasion. Russian citizens are not to blame for their nation’s behaviour, but they do share responsibility.

Removing contributes from the maintainers list is not an extreme action, but it is important as a statement.

As for not feeling the need to defend the Russian citizens, it is nearly righteous for people from nation’s that have been bullied by their neighbours.

He went beyond that. “As a Finn, do you really expect me to up in arms to support the Russians…”

Bravo, slow-clap.

his community can get pretty toxic, predgidist (sp?!?) but also just hostile and combative.

I’ll still get around to opening up an issue

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 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)
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

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

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.

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.

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

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

Kent developed for like 10 years on his own. He’s just having a hard time learning how to play with others, and deal with large priority cycles. He just needs to know that sometime his changes will get pushed to the next cycle.

I use a poopy nano https://ploopy.co/nano-trackball/

Perhaps not useful, but my linux machine doesn’t sleep unless I disconnect my ploopy trackball first, exhibiting the same symptoms.

Zed seems cool, but not much better than other options. I am still kind of thrown off by the immediate GH/CoPilot integration. Am I the an old man left in the caves of feeling that I don’t need the AI help?

Is it ostree based? I guess I should RTM

I like fancy