My situation is remarkably similar to yours down to the language, and I happen to have been considering a US keyboard as well so that’s disheartening to hear. I have nothing to add right now but will let you know if I come across anything helpful!
I love US keyboards for coding, it really improves the experience. Typing in portuguese, however, is not a good experience. The default american layout has the ~ key in a really bad spot. Typing à or ã is REALLY uncomfortable/weird. Fortunately, my keyboard has that key on the right side of the keyboard instead of the left, which greatly improves the experience.
The .XCompose file I linked in the main post is perfect and works great on X11. If you’re not yet on Wayland you can use it and have a great experience.
Right, that all makes sense. I’ll definitely keep that .XCompose file in mind, wasn’t aware it even was a thing before your post. Also, do you mind sharing the specific keyboard you’re using for reference?
Side note, I’ve started using vim/helix a few months ago and the pt layout makes things a lot more awkward than I expected, that’s half the reason I’m considering a US keyboard lol
I’m using an Happy Hacking Keyboard Professional 2. Not most people’s cup of tea but I’ve grown used to it and it’s hard for me to swap to anything else now :P
I can see why it’d be divisive with topre keys, no key markings and a pretty non standard layout but man does it look nice. Really appreciate what they’re going for there.
Anyway, thanks and hope you find a solution, I’ll drop by if I come across anything useful!
You could give this a try instead. It’s a reverse engineered iCue driver which probably supports your keyboard and any other Corsair peripherals you may have.
Well, that’s unfortunate. I have all razer peripherals that work great with openrazer for a back end and polychromatic for a gui front end. I don’t have any corsair devices anymore so I can be much help. Good luck.
X is old and works for the most part but fixing stuff or adding features is hard.
Wayland is new and is supposed to be a successor to X, do what it couldn’t do and don’t repeat the mistakes from it. It should be a drop-in replacement like pipewire but isn’t. Features take long time to develop as devs are engrossed thinking of the best solution to make it happen. A lot of proposed solutions are dismissed as well.
I think the drama around Wayland can be explained by the sentence “it should be a drop-in replacement like pipewire but isn’t”.
Without taking a side on that issue, I will point out that this was not a goal for the Wayland designers ( in their own words - I do not have time to go find a quote but have read this sentiment many times ). Wayland detractors agree with your sentence and, given that expectation, are legitimately upset and even confused that Wayland continues to gain mind and market share against X11.
If you feel that Wayland needs to be a drop-in replacement for X11, it is not ready and may never be. By that metric, some people see Wayland as a failed technology and perceive Wayland users as shills and zealots.
If you are interested in a display server that addresses some of the core design problems in X11 and do not mind moving to something new, Wayland is starting to look ready for prime-time.
If you are non-technical and / or unopinionated the debate is probably irrelevant. Wayland will most likely become the default on whatever Linux distribution you use sometime in 2024 or 2025. You will be a Wayland user. Maybe you already are.
If you are willing to step outside the mainstream, using X11 without Wayland is going to be possible for at least another decade. That said, I am saying “outside the mainstream” because not only will popular Linux distributions and desktop environments start to become Wayland only but the innovation is all going to move to Wayland. There will be many Wayland-only compositors, apps, and features. 5 years from now, not using Wayland is going to really limit the desktop experience. I expect some toolkits ( GTK, Qt, and maybe even WINE ) to drop X11 support at some point ( maybe not soon but sooner than 10 years maybe ). 5 - 10 years may seem like a long time but it will likely come faster than X11 stalwarts expect.
Indeed it won’t modify rar archives. What do you need those for?
The typical flow for rar archives is to unpack them and then either leave the files on disk as plain files or put them into a better archive format such as 7z.
My initial goal (before learning what a headache rar is) was to preserve the original file format. Now my plan is to convert them. I have to confer with my friend to see what format they’d prefer for the files. Probably end up using regular old zip.
It’s more important to make the swap in the first place than it is to pick the right distro, unless you dive straight into LFS or Gentoo or something. You’ll eventually find what you want and can swap easily enough, or you’ll find that you’re happy with what you have!
Both sides are absolutely valid. A complete new install is very easy when you only need to run a few scripts. A small setup with minimal dependencies should also not break that easily when you upgrade your distro release.
I personally always make sure that the way i do things in a distro is the way they intended. That’s how i keep my minimalistic Arch install and multiple larger Debian deployments going for years.
I did some weird stuff with a custom Hue CLI Module for my lab. It’s a fun little, fairly kludgey example of something you could spin up super easily.
In Haskell (much of the time), they say if it compiles it ships! It’s a lazily-evaluated language which lends itself well to a config and it slots right into NixOS quite well since Nix is also a lazily evaluated purely functional language.
yubikey works on every linux distro I have tried, and even on freebsd. Some people say it “works out of the box” but that part is not true on every distro. Every distro will recognize the device when it is plugged in, but not every distro will all 2FA actions out of the box, and almost no distro comes with the management tools.
On linux (and BSD) you can install a CCID tool to get the 2FA, which installs software that needs to be running (you can use the yubikey as a keyboard approach if you really need it) On Linux you can install a manager tool like ykman is easy, if you want to manage the tooling on your card On Linux you can setup PAM (authentication) so that yubikey can be used for logins, sudo auth etc On Linux you can use yubikey to do advanced things like manage the encryption keys for encrypted disks
I appreciate the detailed response. I looked at the Arch wiki page and ensured that I have all packages listed. Still, the output of ykman info is “Error: No YubiKey detected!” :P
I do not get any messages. I’m starting to think there is an issue with my motherboard’s USB-C port. If I can get my hands on a USB-C to USB-A adapter, I can test this theory…
linux
Newest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.