2023/01/17

2023-01-17 00:10:29 +0000abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Read error: Connection reset by peer)
2023-01-17 00:31:03 +0000adramelech[m](~adramelec@2001:470:69fc:105::2:5198)
2023-01-17 03:03:56 +0000banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 268 seconds)
2023-01-17 03:12:25 +0000twiclo1(~twiclo@mail.twil.cx) (Ping timeout: 252 seconds)
2023-01-17 03:25:49 +0000banc(banc@gateway/vpn/protonvpn/banc)
2023-01-17 03:56:24 +0000td_(~td@83.135.9.45) (Ping timeout: 260 seconds)
2023-01-17 03:58:15 +0000td_(~td@83.135.9.4)
2023-01-17 04:58:35 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 260 seconds)
2023-01-17 05:09:07 +0000lokesh1197(~Thunderbi@14.139.128.40)
2023-01-17 05:14:20 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds)
2023-01-17 05:21:41 +0000piele(~piele@tbonesteak.creativeserver.net) (Ping timeout: 255 seconds)
2023-01-17 05:36:26 +0000lokesh1197(~Thunderbi@14.139.128.40) (Ping timeout: 256 seconds)
2023-01-17 05:37:24 +0000lokesh1197(~Thunderbi@14.139.128.10)
2023-01-17 05:38:31 +0000lokesh1198(~Thunderbi@14.139.128.10)
2023-01-17 05:41:59 +0000lokesh1197(~Thunderbi@14.139.128.10) (Ping timeout: 260 seconds)
2023-01-17 05:43:36 +0000lokesh1198lokesh1197
2023-01-17 05:50:36 +0000lokesh1197(~Thunderbi@14.139.128.10) (Ping timeout: 256 seconds)
2023-01-17 06:45:17 +0000yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de) (Quit: Leaving)
2023-01-17 06:58:21 +0000yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de)
2023-01-17 08:49:35 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-17 08:57:15 +0000cfricke(~cfricke@user/cfricke)
2023-01-17 09:23:42 +0000piele(~piele@tbonesteak.creativeserver.net)
2023-01-17 09:47:49 +0000[Leary](~Leary]@user/Leary/x-0910699) (Remote host closed the connection)
2023-01-17 09:48:26 +0000[Leary](~Leary]@user/Leary/x-0910699)
2023-01-17 09:53:39 +0000lokesh1197(~Thunderbi@14.139.128.10)
2023-01-17 10:10:42 +0000lokesh1197(~Thunderbi@14.139.128.10) (Read error: Connection reset by peer)
2023-01-17 10:12:59 +0000lokesh1197(~Thunderbi@14.139.128.10)
2023-01-17 10:13:45 +0000lokesh1197(~Thunderbi@14.139.128.10) (Client Quit)
2023-01-17 10:14:06 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 256 seconds)
2023-01-17 10:23:46 +0000ft(~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving)
2023-01-17 11:20:48 +0000lokesh1197(~Thunderbi@14.139.128.10)
2023-01-17 11:24:52 +0000lokesh1197(~Thunderbi@14.139.128.10) (Read error: Connection reset by peer)
2023-01-17 11:34:12 +0000lokesh1197(~Thunderbi@14.139.128.10)
2023-01-17 12:00:04 +0000minnie(~minnie@159.196.202.199) (Ping timeout: 256 seconds)
2023-01-17 12:12:04 +0000lokesh1197(~Thunderbi@14.139.128.10) (Remote host closed the connection)
2023-01-17 12:27:28 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-17 12:47:26 +0000minnie(~minnie@159.196.202.199)
2023-01-17 13:06:56 +0000Guest24(~Guest24@41.205.148.9)
2023-01-17 13:07:24 +0000Guest24(~Guest24@41.205.148.9) (Client Quit)
2023-01-17 13:57:02 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 265 seconds)
2023-01-17 14:00:27 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-17 14:29:18 +0000piele(~piele@tbonesteak.creativeserver.net) (Quit: Ciao!)
2023-01-17 14:38:53 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 260 seconds)
2023-01-17 14:47:22 +0000piele(~piele@tbonesteak.creativeserver.net)
2023-01-17 15:07:31 +0000cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.7.1)
2023-01-17 15:31:55 +0000gdd(~gdd@2001:470:1f13:187:e8a5:fbff:fe29:42f5) (Ping timeout: 248 seconds)
2023-01-17 15:54:33 +0000gdd(~gdd@2001:470:1f13:187:41fc:3586:85ea:bc08)
2023-01-17 16:03:52 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-01-17 16:06:15 +0000minnie(~minnie@159.196.202.199) (Ping timeout: 260 seconds)
2023-01-17 17:04:40 +0000Guest56(~Guest56@41.182.26.122)
2023-01-17 17:10:15 +0000Guest56(~Guest56@41.182.26.122) (Quit: Client closed)
2023-01-17 17:52:02 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-17 18:15:40 +0000 <T_X> how do people usually handle applications which need many modifier keys. like flight simulators. where I would have conflicts with the Xmonad modifier key. but where I also don't have any "spare" modifier keys as is
2023-01-17 18:15:53 +0000liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-01-17 18:16:07 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2023-01-17 18:17:18 +0000 <vrs> almost nothing binds capslock and even if you've bound it to esc, you might have an app-specific binding
2023-01-17 18:19:59 +0000 <T_X> would it in theory be possible to somehow implement something in (the) xmonand (config) which: if pressing Alt+AltGr at the same time would toggle whether Xmonad reacts to any other Xmonad shortcut?
2023-01-17 18:20:07 +0000 <T_X> *xmonad
2023-01-17 18:21:34 +0000 <T_X> capslock is not available for me either, as I use it for my Neo2 keyboard layout: https://www.neo-layout.org/
2023-01-17 18:22:29 +0000 <T_X> and the sim application I'm trying does not recognize this (modified) capslock key as a valid modifier
2023-01-17 18:25:40 +0000 <T_X> and this sim needs all these modifiers individually by default :D: LCtrl, RCtrl, LShift, RShift, Alt, AltGr, LWin
2023-01-17 18:28:31 +0000 <T_X> and with Sonic-Pi I also had some issues. as it uses the Alt key if I remember correctly. with no configuration to change it
2023-01-17 18:31:43 +0000 <T_X> while I really prefer using the Alt key for Xmonad, as one of the most accessible ones from the thumb, least tiring for me :D
2023-01-17 18:34:58 +0000 <geekosaur> there's no good way to do this, unfortunately
2023-01-17 18:36:02 +0000 <geekosaur> hypothetically you could have a keybind which removed all the keybindings except itself, but they'd come back on the next MappingNotify event
2023-01-17 18:36:15 +0000 <geekosaur> and those are surprisingly common
2023-01-17 18:45:22 +0000 <vrs> ugh it turns out that pango understands "green" as #008000 and not #00ff00
2023-01-17 18:45:51 +0000 <vrs> that explains why the colors in my xmobar were suddenly so subdued
2023-01-17 19:04:14 +0000ft(~ft@p4fc2a257.dip0.t-ipconnect.de)
2023-01-17 19:10:44 +0000mc47(~mc47@xmonad/TheMC47)
2023-01-17 19:34:48 +0000 <Solid> wat
2023-01-17 19:36:02 +0000 <geekosaur> this is why I used hex codes and not color names in my pango markup for xmonad-log-applet
2023-01-17 19:36:11 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 264 seconds)
2023-01-17 20:09:24 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-17 20:43:01 +0000 <HB[m]> You get used to it and it's much better than color names.
2023-01-17 20:43:55 +0000 <HB[m]> 00-FF = 0-255 R, G and B. Adjust how you like. Names are difficult to remember.
2023-01-17 20:45:33 +0000 <HB[m]> 220000 is maroon. FF0000 is bright red. FF9999 is kind of less intense pinkish red, as you add more grey to it.
2023-01-17 20:46:18 +0000 <HB[m]> It it easier to imagine in number values of how much of each light you want to mix. It's like how to make secondary and tertiary colors from a the three primcolors. As in painting. :)O
2023-01-17 20:46:20 +0000 <HB[m]> s/primcolors/prime colors/, s/:)O/🙂/
2023-01-17 21:48:26 +0000mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-01-17 23:34:24 +0000 <[Leary]> T_X: You could use X.H.Modal to switch to and from a non-interference mode where xmonad gives up almost all of its bindings.