jaxxed

Honestly, in the long term it has been less effort.

If you’re an “out-od-the-box” comouter user (web browser, maybe one or two apps, and office suite, then stick with the more conventional distros. If you are very dynamic with your OS, especially 8f you play with a lot of different OSS applications, then Arch get’s easier.

I am thinking of different “theys”. I am not wait8ng for steam to give me a desktop. I am not waiting for kde to take this seriously.

I am hoping that some of the very talented teams that manage small wms, who come up with interesting ways to interact with your apps, to get interwsted in tue developer kit.

I think that I said it above, that I think that paperwn / niri / karousel are the best starting points.

I tuink that I understand what steam is selking, but I don’t think that a windowed wm is ideal as a desktop with VR. I get that we are takking about a computer strapped to your head.

The karousel guy could take a stab at it, but if Steam releases a dev kit, then any team could try developing a wm with workflows that are designed around a VR interface.

They’re releasing an SDK, which most likely will include a linux compatibility. Windowing desktops may not be the right starting point for a VR desktop, but hopefully some of the teams will grab the developers kit and consideration VR centric ways of working with applications.

are there any linux WMs that provide a good desktop experience with VR headsets yet? I’d love to get a niri like scrolling experience with goggles - although it would make meetings weird.

Which surface do you use? And what features are missing still?

Not an expert though, but have been watching bcachefs for … what feels like a decade.

It’s marked as experimental, hence the “experimental”

To be more clear, before he got his code mainlined, you needed to run h8s full fork of the kernel, with changes made not just to the cache code itself, but also to other parts.

Not all of his changes went in though; but the differences got sorted out enough that the vast majority of his newer changes were driver only.

That said, he was still ruffling feathers about wanting some fast moving kernel changes.

Definitely not going anywhere near the comments section on that phoronix article. It’s guaranteed to be pure poison.

I agree, on both statements.

It is easily stable enough for experimental use.

Additionally, Kent got most of his kernel changes needed for bcachefs merged already, so a dkms should be easier to manage now.

The Unix philosophy is many parts combined, instead of one mega-part. The Linux kernel is an exception, but the concept allows Linux to evolve over time, and to be flexible. I don’t know what AHK does (consider describing behaviour in these kinds of posts), but concepts like uber-key mapping can’t exist the way they did in Windows.

It seems to me that you have two options:

1. Move to a launcher style approach: find a utility that let’s you trigger a menu that offers the things that your are trying to do (dmenu, fuzzel have lots of extensions for behaviours), similar to the OSX launchpad or the windows start menu w/typing, but you can create your own options and script them
2. Look at the key mapping for your DE (kde, gnome, sway, xfce, niri) and see what is there. KDE has excessive key mapping, and the small tiling managers have many launching and scripting options.

Listen, moving from windows to Linux is not like moving to an apartment across the hall, it is more like moving to an apartment across the border - they have worked out some things differently, and sometimes better. Half of the goal of moving away from windows is moving away from windowisms. Explore and what else is there.

People ask me why I use emacs (they don’t actually, but they could) and I answer by telling them that there are some very new progressive workflows that are significantly better that most IDEs - look at consult/vertico/marginalia/orderless/corfu , and forget evil/vi, look at meow. File browsing using a tree navigator is a last ditch thing. Watch prot on YouTube to learn build a stone cabin, understand philosophy, and learn how to use emacs; move forward and progress.

Darnit, I’m rambling again.

Easy installer too.

Sysexts are something I’ve been meaning to get in to. Have you had much success in general with them?

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