2023/03/01

2023-03-01 05:10:55 +0000Diablo-D3(foobar@exelion.net) (Ping timeout: 246 seconds)
2023-03-01 05:17:34 +0000Diablo-D3(foobar@exelion.net)
2023-03-01 05:27:24 +0000Diablo-D3(foobar@exelion.net) (Remote host closed the connection)
2023-03-01 05:27:49 +0000Diablo-D3(foobar@exelion.net)
2023-03-01 10:38:34 +0000b50d(~b50d@62.96.54.30)
2023-03-01 12:56:17 +0000Bayes(~Bayes@user/bayes) (*.net *.split)
2023-03-01 13:00:58 +0000Bayes(~Bayes@user/bayes)
2023-03-01 16:53:58 +0000b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2023-03-01 17:02:40 +0000 <piraty> after i went full-nerd with keymaps on my new split, which i fried with ESD very recently, i now realize i need kmonad on traditional keyboards.
2023-03-01 17:06:52 +0000utis(~utis@s176125235117.blix.com)
2023-03-01 17:08:36 +0000 <utis> is it possible to do something when a given set (or number) of keys are down simultaneously, having been pressed in any order?
2023-03-01 17:48:34 +0000 <piraty> technically: if the keycodes were not sent yet, sure. i don't know if kmonad can though
2023-03-01 17:48:46 +0000 <piraty> what is your use-case–
2023-03-01 18:38:35 +0000 <utis> cat lock
2023-03-01 18:42:12 +0000 <utis> it's asking a bit much i suppose
2023-03-01 20:05:15 +0000utis(~utis@s176125235117.blix.com) (Ping timeout: 268 seconds)