Sexy anti-woke task force officer?

Bobby Fingers has the best definition of “woke,” one that I feel all can agree with, even if they are dismayed by the quality of his dashboards.

The lizardfolk brigade.

In 2016, 96% of UKIP membership voted for (some version of) Brexit - their raison d’etre. 4% is a typical fraction of any group to be chaotically bonkers.

Thank-you.

And 51 feels prime. Someone sgould write a letter.

It’s “revelation,” singular. Like trivial pursuit.

The way the electoral roll is managed varies from place to place.

Avoiding automatic voter registration tends to favour the more traditionally conservative demographic; it’s racist and classist, but the people who turn up to vote on local electoral issues are too, by and large. It requires engagement to change.

You’ve linked into it, but I was just going to point at the Git book: https://git-scm.com/book/en/v2

It’s an afternoon’s reading; it does an excellent job of giving you the right mental model - and a crib aheet of commands to navigate it.

I have observed people taking Rust seriously. You need to reexamine your assumptions.

We have an evolved capability to short-circuit decisions with a rapid emotional evaluation. It means as a species we didn’t die out early [“that’s a lion; I’m a oerson; lions eat people ergo… Agh!” is not a sustainable strategy] - what’s amazing is that we can also apply it to elarned abstract things like an aestetic sense about programming languages. Such instincts aren’t always perfect, but they’re still worth paying attention to. I don’t see a reason not to express that in a blog post, but you can replace it with “this is unergonomic and in some cases imprecise” if you prefer.

That seems like quite a lot of booms.

FWIW I was trying to do something like this and ended up with pretty much what you describe - some custom shading to get everything working.

“Maybe our friend doesn’t like monads.”

Netware was rock solid.

Minimise your windows one at a time and check that the gnome keyring hasn’t popped up a dialog box sonewhere behind everything else that’s asking you if it’s okay to proceed.

It does rather sound like proposing an immediate 25k hike in house prices, yeah.

It’s the gnome key ring ssh agent.

It’s possible that this has popped up a window asking gor permission / a passphrase / something and you’re not seeing that.

That’s only part of the handshake. It’d require agent input around that point.

Is this problem a recurring one after a reboot?

If it is it warrants more effort.

If not and you’re happy with rhe lack of closure, you can potentially fix this: kill the old agent (watch out to see if it respawns; if it does and that works, fine). If it doesn’t, you can (a) remove the socket file (b) launch ssh-agent with the righr flag (-a $SSH_AGENT_SOCK iirc) to listen at the same place, then future terminal sessions that inherit the env var will still look in the right place. Unsatisfactory but it’ll get you going again.

Okay, that agent process is running but it looks wedged: multiple connections to the socket seem to be opened, probably your other attempts to use ssh.

The ssh-add output looks like it’s responding a bit, however.

I’d use your package manager to work out what owns it and go looking for open bugs in the tool.

(Getting a trace of that process itself would be handy, while you’re trying again. There may be a clue in its behaviour.)

The server reaponse seems like the handshake process is close to completing. It’s not immediately clear what’s up there I’m afraid.

Please don’t ignore the advice about SSH_AGENT_SOCK. It’ll tell yoy what’s going on (but not why).