2023/03/01

2023-03-01 06:10:55 +0100Diablo-D3(foobar@exelion.net) (Ping timeout: 246 seconds)
2023-03-01 06:17:34 +0100Diablo-D3(foobar@exelion.net)
2023-03-01 06:27:24 +0100Diablo-D3(foobar@exelion.net) (Remote host closed the connection)
2023-03-01 06:27:49 +0100Diablo-D3(foobar@exelion.net)
2023-03-01 11:38:34 +0100b50d(~b50d@62.96.54.30)
2023-03-01 13:56:17 +0100Bayes(~Bayes@user/bayes) (*.net *.split)
2023-03-01 14:00:58 +0100Bayes(~Bayes@user/bayes)
2023-03-01 17:53:58 +0100b50d(~b50d@62.96.54.30) (Remote host closed the connection)
2023-03-01 18:02:40 +0100 <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 18:06:52 +0100utis(~utis@s176125235117.blix.com)
2023-03-01 18:08:36 +0100 <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 18:48:34 +0100 <piraty> technically: if the keycodes were not sent yet, sure. i don't know if kmonad can though
2023-03-01 18:48:46 +0100 <piraty> what is your use-case–
2023-03-01 19:38:35 +0100 <utis> cat lock
2023-03-01 19:42:12 +0100 <utis> it's asking a bit much i suppose
2023-03-01 21:05:15 +0100utis(~utis@s176125235117.blix.com) (Ping timeout: 268 seconds)