It is essentially an equivalence gate: A==B.

At least one for each manufacturer that uses it under the hood in a Tivo-like manner

Sometimes they need to be upset before they realise what they did wrong.

Judo.

You likely need to tell the uefi software to boot Grub. I can’t remember the command off the top of my head sorry but you basically need to tell it what to boot by default. Then you can let Grub handle the choice of Linux or windows. I just set up a laptop for my sister that behaved that way. No matter what I selected as default in the uefi setup it kept resetting back.

Just looked it up, efibootmgr is the command I think. https://www.linuxbabe.com/command-line/how-to-use-linux-efibootmgr-examples

I’d be happy to find an alternative to Hyprland, but it was the first tiling manager that really clicked for me and (before the community issues came to light) I spent quite some time getting it set to the way I like it. I’d love for a competent fork or similar but it is well beyond my skill level to do that.

Do you have examples of this? Not being contrarian, I actually run Hyprland myself. I’m just curious where the limitations of wlroots have been.

I really recommend the YouTube channel “Another Roof”. His first few videos were building up exactly this idea, as well as building up all the real numbers (possibly complex too if I’m remembering correctly). Sounds like a dry topic but he uses humour really well throughout. https://youtube.com/@anotherroof

Here is a playlist of the topic: https://youtube.com/playlist?list=PLsdeQ7TnWVm_EQG1rmb34ZBYe5ohrkL3t

SUSiE

TRANSPARENT TERMINALS! Haha it felt so futuristic and to this day I can’t run a terminal without a little transparency. Enlightenment was my first experience of it.

Yeah, definitely needed to move on after so long but I certainly learnt a lot from it!

I was pretty much thrown in and learnt on the job. I shadowed another technician for a bit that showed the basic maintenance servicing steps for the major machines, but then went out on my own. I’m in Australia and we had instruments in all major cities as well as New Zealand, so it involved a lot of flying around and fitting in as many customers as possible. So I had to be able to troubleshoot fast and ideally fix things on the spot.

Often it involved figuring out a temporary workaround whilst a part would need to be ordered from the US or similar issues. My main skillset was being able to think quickly like this and improvise. Being able to understand exactly what a machine is doing (not just the theory the lab techs were thinking about, actual things like gas fill reservoir A, valve 3 open to reservoir B with vacuum guage etc) was more important than anything else I feel. Especially considering we were a small company so couldn’t afford to carry around every conceivable spare part, not much of the machinery was based on off-the-shelf parts so we mostly carried the most likely parts to be needed in general.

My IT background was mostly useful for dealing with the inevitable issues with their terrible 16-bit era (!!) software and trying to get it running on Windows 10. Of course the manufacturer wanted them to just replace the system with the new model, but they were exactly the same internals with just newer controller cards running (very very slightly) updated software. This would cost up to a quarter of a million dollars, so you can imagine that not many customers were excited to jump on that!

I would say the automotive technician skillset likely overlaps a little better, especially if they are from the electrical side. My IT skills were useful as I mentioned (and I could talk-the-talk with the university or corporate IT teams in order to get required permissions etc) but most of the harder problems were physical and electronic in nature. As you mentioned, I was interested in the science part too, and funnily enough a couple of the universities got me in to teach the theory of what the systems were measuring, which I literally just figured out on the job haha

Of course, this all depends on exactly what kind of equipment you are talking about. For reference, I mostly dealt with gas adsorption, mercury porosimetry, laser or vision particle sizing and helium pycnometry. We also worked with a few other bits and pieces here and there, but that was the vast majority.

Oh, in terms of pay, I took a massive pay cut to work there. I’d been in IT for about 12 years and needed a change. I knew the boss of the company from Judo training and he asked if I’d be interested in joining. Not the most normal career path but I figured it sounded interesting.

Sorry for the rambling structure, I’m at work and was jumping back and forth to here as I could.

Mostly on the job learning. Had an IT background and basic electronics skills including crude soldering at the time, but mostly I was just good at troubleshooting and thinking through problems. Every machine was very specialised so it was hard to get much info and a lot of problems were unique to that machine for that user with that sample in that condition…

My old job was servicing niche scientific equipment. Glad to see you saw that opportunity - there are a lot of shitty products out there selling for five or six figures, and often running technology multiple decades out of date.

Hearing your monitor squeal when you got the modelines wrong was fun.

Currently using gbar in Hyprland as I got a bit overwhelmed trying to learn too many things at once (gbar is very limited but simple to configure). I’ve always been thinking of moving over to a more flexible option like eww though, and this might be a good reason to do so (keeping things consistent).

### Multiple binds to one key [](https://wiki.hyprland.org/Configuring/Binds/#multiple-binds-to-one-key)

You can trigger multiple actions with one keybind by assigning multiple binds to one combination, e.g.:

# to switch between windows in a floating workspace
bind = SUPER,Tab,cyclenext,          # change focus to another window
bind = SUPER,Tab,bringactivetotop,   # bring it to the top

The keybinds will be executed in the order they were created. (top to bottom)

That’s just the way you write the rules being deprecated, not the functionality.

There is move left/right within a workspace, move to specific workspace and then move to next/previous workspace (from memory using e+1 as the workspace name in the command but might be misremembering). Admittedly this isn’t exactly the same as what you want; I replied from my mobile and checked when I went back to my desk. I usually use meta/shift/[num] to send to a specific workspace though as I make heavy use of them.

I have workspaces pinned to monitors in Hyprland and have none of the problems you mentioned. I use odd numbers for left screen and even numbers for right.

Edit: just took a look and can’t find mention of the depreciation; where did you read that?

Considering they specifically removed Linux support of the earlier headsets, I doubt it too.