2023/01/26

2023-01-26 01:33:42 +0100ghormoon(~ghormoon@ghorland.net) (Ping timeout: 255 seconds)
2023-01-26 02:02:08 +0100ghormoon(~ghormoon@ghorland.net)
2023-01-26 02:27:09 +0100telser_(~quassel@user/telser) (Ping timeout: 256 seconds)
2023-01-26 02:27:37 +0100telser(~quassel@user/telser)
2023-01-26 03:15:14 +0100blaa(~bla@83.24.73.237.ipv4.supernova.orange.pl)
2023-01-26 03:15:59 +0100bla(~bla@83.24.70.42.ipv4.supernova.orange.pl) (Ping timeout: 260 seconds)
2023-01-26 03:37:37 +0100rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Quit: WeeChat 3.0)
2023-01-26 04:03:32 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 255 seconds)
2023-01-26 04:13:43 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-01-26 04:24:29 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-01-26 04:47:27 +0100td_(~td@i53870930.versanet.de) (Ping timeout: 252 seconds)
2023-01-26 04:49:10 +0100td_(~td@i53870925.versanet.de)
2023-01-26 06:10:06 +0100thunderrd(~thunderrd@183.182.111.166) (Read error: Connection reset by peer)
2023-01-26 06:10:39 +0100thunderrd(~thunderrd@183.182.111.166)
2023-01-26 07:06:47 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds)
2023-01-26 07:36:14 +0100 <Solid> I think it would be valuable to have the core natively support [(KeyMask, KeySym)] bindings, making submap obsolete alltogether (perhaps even integrating NamedActions while we're at it)
2023-01-26 07:36:22 +0100 <Solid> But realistically that's never going to really happen, is it?
2023-01-26 07:56:44 +0100qbt(~qbt@user/edun)
2023-01-26 09:59:46 +0100ft(~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving)
2023-01-26 10:00:04 +0100nihilipster[m](~nihilipst@2001:470:69fc:105::720) (Quit: You have been kicked for being idle)
2023-01-26 10:00:10 +0100unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-01-26 10:27:20 +0100jludwig(~justin@li657-110.members.linode.com) (Ping timeout: 246 seconds)
2023-01-26 10:30:18 +0100jludwig(~justin@li657-110.members.linode.com)
2023-01-26 10:49:16 +0100T_X(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2023-01-26 10:49:24 +0100T_X(~T_X@diktynna.open-mesh.org)
2023-01-26 11:28:06 +0100 <geekosaur> it might be an option for 1.1 since we're already looking at making a major change
2023-01-26 11:28:21 +0100unclechu(~unclechu@2001:470:69fc:105::354)
2023-01-26 11:56:14 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 246 seconds)
2023-01-26 11:56:45 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-01-26 12:28:00 +0100qbt(~qbt@user/edun) (Ping timeout: 248 seconds)
2023-01-26 14:36:16 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-01-26 14:42:39 +0100kalj(~kalj@78-71-20-170-no193.tbcn.telia.com)
2023-01-26 15:07:10 +0100fjMSX(~hypni2p@89-179-32-81.broadband.corbina.ru)
2023-01-26 15:37:15 +0100kalj(~kalj@78-71-20-170-no193.tbcn.telia.com) (Quit: Client closed)
2023-01-26 17:00:04 +0100AngryBromide[m](~angrybrom@2001:470:69fc:105::1:cfb3) (Quit: You have been kicked for being idle)
2023-01-26 17:00:09 +0100unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-01-26 17:28:37 +0100Jadesheit[m]Jadeitits[m]
2023-01-26 19:03:49 +0100ft(~ft@p4fc2a257.dip0.t-ipconnect.de)
2023-01-26 19:09:00 +0100tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
2023-01-26 19:57:11 +0100Digit(~user@user/digit) (Ping timeout: 256 seconds)
2023-01-26 21:28:07 +0100thyriaen(~thyriaen@2a01:aea0:dd4:4fa4:6245:cbff:fe9f:48b1)
2023-01-26 21:29:00 +0100 <thyriaen> I found a strange bug
2023-01-26 21:29:11 +0100 <thyriaen> I am using XmonaD on 2 screens
2023-01-26 21:29:14 +0100unclechu(~unclechu@2001:470:69fc:105::354)
2023-01-26 21:29:30 +0100 <thyriaen> when i type xrandr --output monitor-2 --off
2023-01-26 21:30:07 +0100 <thyriaen> xmonad does something really strange - it only puts screens on the first 2/3 of the screen and leaves the bottom third empty
2023-01-26 21:30:58 +0100 <thyriaen> could be because my second screen is in vertical position but i am not sure -- any ideas ? ( restarting xmonad fixes it ) but it would be nice if i could toggle my 2nd screen on and off
2023-01-26 21:32:01 +0100 <geekosaur> that's odd. rescreening should work fine, absent video driver bugs (restarting xmonad wouldn't help in that case, unless you also mean restarting the X server)
2023-01-26 21:33:02 +0100 <geekosaur> I mean, I see that if I hotplug a monitor, but I also see it if it's sitting at the login screen (tested with both lightdm and gdm, also with gnome instead of xmonad)
2023-01-26 21:37:36 +0100 <geekosaur> does mod-n help, by any chance? it should force a rescreen
2023-01-26 22:04:27 +0100mc47(~mc47@xmonad/TheMC47)
2023-01-26 23:13:03 +0100mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)