[rhn_mk1]

> PrintScreen between right Alt and right Ctrl: very important too

Please don't. Unless you want users of language layouts that make use AltGr to suffer.

Imagine typing away a message, accidentally slipping your finger from AltGr onto the PrintScr (actually SysRq), and triggering a sysrq reboot in linux. Regularly.

It's a choice between triggering crashes _all the time_, or disabling sysrq and never being able to debug the legit ones.

[csdvrx]

> Please don't.

Please do!

Because even with the most generous interpretation of your issue, it seems fully self-inflicted, by a lack of typing skills compounded by refusing to configure the keymap or the sysreq bitmask, and asking instead for that to become everyone problem by having the key moved!

> accidentally slipping your finger from AltGr onto the PrintScr

What about learning to touchtype? And until them, typing in a well lit room?

> It's a choice between triggering crashes _all the time_, or disabling sysrq and never being able to debug the legit ones.

That's a false dichotomy. You are not triggering crashes, you are instructing your computer to reboot (sysreq B) which it does.

It should not be blamed on the computer, but on your lack of attention, and the lack of adaptation, so I'd even call that a self inflicted problem.

If you can take the time to configure your laptop to use a non standard layout, you can certainly take the extra time to learn proper typing instead of bothering the vast majority of those who are happy with this layout.

If you can't take that time, you can certainly apply one of the many possible counter measures, like moving sysreq to another key (cf dumpkeys and loadkeys), or just disabling the sysreq reboot function (0 disables sysreq, 1 enables it, but you can have a finer control if you read the documentation, ex: 128 is the bitmask for the reboot/poweroff) which would let you debug the "legit ones" - though if your linux has legit crashes, you may have bigger problems!

[rhn_mk1]

> fully self-inflicted, by a lack of typing skills compounded by refusing to configure the keymap or the sysreq bitmask

So, git gud? Sorry, I'm not buying it. People have different motor skills, you know. You can't always make your body physically perfect.

Changing the mapping might work (although I doubt it, it's a deep kernel mechanism that probably avoids such complexity), but requires having the knowledge that it's even possible and how to do it. Sadly, laptops don't come with the instructions. And why should they? Machines should be made well in the first place.

Oh, and setting a mask doesn't help because b, c, e, i, k, o, r, u, all have nasty consequences.

[csdvrx]

> So, git gud?

If if's bothering you as much as you said, YES, stop complaining, and start acting on your complaints!

I've already given you all the pointers.

Now I'll help you more if you need.

> Sorry, I'm not buying it.

Neither am I. I get the feeling you want to complain more than you want to actually solve your problem. But as this is HN, I'm giving your comment the most positive interpretation possible.

> People have different motor skills, you know. You can't always make your body physically perfect.

So you don't want to try or, due to physical limitations, can't train better fine motor skills to be on par with about 90% of the regular population? Not very plausible, but why not!

Still, this leaves remapping Sysrq or configuring the bitmask, so I'll guide you though the keymap fixing if you need (even if I hope I won't have to, and that you'll be able to learn by yourself with the right pointers)

> Changing the mapping might work (although I doubt it, it's a deep kernel mechanism that probably avoids such complexity),

With computers, there is no place for philosophical doubts: you try it, and note the results of the experiment: either it does work, or it doesn't work. And if it doesn't, you can make it do so by reading the code, understanding then changing it.

So first, did you try it? If not, why? If you did, what did you observe?

BTW if you didn't, let me remove some of your doubts: dumpkeys and loadkeys are all that you need to change the sysreq mapping: the "deep kernel mechanism" links an action with a key through a table, defined in software.

This is just like how the same key can trigger a Y or a Z (US vs German keyboards) - and yes, you can change that too if you don't like it.

To have a look at this tablet, outside X or Wayland (ex: chvt 1), do:

dumpkeys > current.map

Edit it with your favorite editor to move Sysrq to where you want ex (ex: Insert key?).

You can also add any other changes you want (like, keep both your alt as regular alt, and instead make something else the 3rd level key - say the right ctrl key?)

> requires having the knowledge that it's even possible and how to do it.

Yes, this is called having agency. But here, I gave you the knowledge! Do you have another complain/excuse? Or are you willing to try to fix the problem now?

BTW regarding "agency", I don't use Linux as a daily driver- I prefer Windows, not just because it's less elitist, but due to the better terminal options and the greater hackability of its GUI. You don't have to use Linux if you don't like it! There are many things I dislike in Linux myself.

> Sadly, laptops don't come with the instructions.

You'll find most of the instructions you want (and more!) on the Arch wiki.

But if it doesn't exist or if it's not accessible enough, what about writing some?

Personally, I'm preparing a tutorial to help people with a specific tablet (great hardware, but bad software and configuration OOB, so most people hated it, which I find sad)

Maybe you could do the same, as other people may be inconvenienced by the same problem you are having, and would benefit from your solution?

> And why should they

Because you or someone else (say me!) cares enough to want to hack they hardware to do their bidding? Because it fun?

> Machines should be made well in the first place.

Different people want different things.

Some tastes can't be reconciled.

> Oh, and setting a mask doesn't help because b, c, e, i, k, o, r, u, all have nasty consequences.

Do you really want/need me to also write your bitmask for you? Select the ones you won't want, and mask them out

But again, you should take the easy way out: just remap Sysrq to another key that's away from your fingers, and call it a day! You could have done this remapping in less than half the time it took you to write this complain!

[rhn_mk1]

> start acting on your complaints!

I just did: I raised an objection to a bad idea for anyone who might be misled by it. Also I won't buy a computer with this flaw.

> So first, did you try it? If not, why?

I did not, because I did not know how. I also don't want to know how to alter my computer to achieve a basic minimum of functionality, because a minimum is what is assumed. Either the OS or the hardware should have sane defaults.

> Different people want different things.

I suggest you remap your keys (when you use Linux) to fit your special need then ;)

[csdvrx]

>> So first, did you try it? If not, why?

>I did not, because I did not know how.

Now you do

> I suggest you remap your keys (when you use Linux) to fit your special need then ;)

When there is no physical key, like to the left and right of the up arrow where pagedown and pageup would be, I can't invent them out of thin air.

[rhn_mk1]

There's typically the "emulate a right click" button or a Windows button in between AltGr and Ctrl. Those don't have the faults of a SysRq, so they seem like good candidates for a new hypothetical keyboard.