2022/06/23

2022-06-23 00:56:39 +0200werneta(~werneta@137.78.30.207) (Ping timeout: 268 seconds)
2022-06-23 00:58:12 +0200werneta(~werneta@137.79.203.93)
2022-06-23 01:03:08 +0200alternateved(~alternate@82.180.151.239) (Remote host closed the connection)
2022-06-23 01:24:14 +0200esrh(~user@sw-10121.atl5.as22384.net)
2022-06-23 01:46:58 +0200werneta(~werneta@137.79.203.93) (Ping timeout: 240 seconds)
2022-06-23 01:57:06 +0200esrh(~user@sw-10121.atl5.as22384.net) (Ping timeout: 264 seconds)
2022-06-23 01:59:42 +0200mvk(~mvk@2607:fea8:5ce3:8500::4588)
2022-06-23 02:14:21 +0200logzet(~quassel@2001:9e8:e527:7100:dabb:c1ff:fed3:a1b9) (Ping timeout: 268 seconds)
2022-06-23 02:14:24 +0200logzet_(~quassel@2001:9e8:e539:f900:dabb:c1ff:fed3:a1b9)
2022-06-23 02:15:42 +0200logzet_(~quassel@2001:9e8:e539:f900:dabb:c1ff:fed3:a1b9) (Client Quit)
2022-06-23 02:23:09 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-06-23 03:02:18 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 240 seconds)
2022-06-23 04:03:05 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 248 seconds)
2022-06-23 04:24:44 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-06-23 04:46:18 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1)
2022-06-23 04:54:49 +0200mvk(~mvk@2607:fea8:5ce3:8500::4588) (Ping timeout: 248 seconds)
2022-06-23 05:01:28 +0200td_(~td@muedsl-82-207-238-203.citykom.de) (Ping timeout: 268 seconds)
2022-06-23 05:02:50 +0200td_(~td@94.134.91.184)
2022-06-23 05:07:59 +0200hipurus(~hipurus@184.4.83.175)
2022-06-23 05:08:58 +0200hipurus(~hipurus@184.4.83.175) (Client Quit)
2022-06-23 07:38:27 +0200neoatnebula(~neoatnebu@49.206.16.59)
2022-06-23 09:35:20 +0200benin0(~benin@183.82.30.117)
2022-06-23 09:41:40 +0200neoatnebula(~neoatnebu@49.206.16.59) (Quit: Client closed)
2022-06-23 10:11:44 +0200cfricke(~cfricke@user/cfricke)
2022-06-23 11:00:11 +0200AntonioRomano[m](~cidramatr@2001:470:69fc:105::2:7b0) (Quit: You have been kicked for being idle)
2022-06-23 11:00:46 +0200alternateved(~alternate@37.120.211.165)
2022-06-23 11:37:50 +0200chomwitt(~chomwitt@2a02:587:dc0d:e600:4907:a32:4c72:2e8c)
2022-06-23 12:09:45 +0200alternateved(~alternate@37.120.211.165) (Remote host closed the connection)
2022-06-23 12:11:27 +0200alternateved(~alternate@37.120.211.165)
2022-06-23 12:34:29 +0200 <liskin> Solid: I went to our office today and there are 27" 4k (3840x2160) displays and it kinda looks like 27" is twice 14" so I thought I'd just sit near the display and keep my 7x13 fixed font, but… I think I've reached the limit of my eyesight :-)
2022-06-23 12:35:03 +0200 <liskin> 9x18 is fine, and those antialiased fonts in browser are also almost acceptable
2022-06-23 12:35:27 +0200 <liskin> but non-curved 27" so close to my face is unergonomic :-(
2022-06-23 12:45:17 +0200 <liskin> also why the fuck is this thing only doing 30 hz :-/
2022-06-23 12:50:30 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Ping timeout: 264 seconds)
2022-06-23 12:52:24 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-06-23 13:52:14 +0200mc47(~mc47@xmonad/TheMC47)
2022-06-23 14:38:45 +0200 <dminuoso> liskin: You wondered about the aliasing on my laptop screen right?
2022-06-23 15:56:19 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.5)
2022-06-23 15:59:49 +0200cfricke(~cfricke@user/cfricke)
2022-06-23 16:01:48 +0200vanvik(~vanvik@78.156.12.223) (Quit: Later)
2022-06-23 16:02:10 +0200vanvik(~vanvik@78.156.12.223)
2022-06-23 16:03:20 +0200 <liskin> dminuoso: yeah that was probably me but I think we concluded I was just hungover
2022-06-23 16:04:06 +0200 <liskin> you have more or less exactly the same display in terms of size and resolution as I have
2022-06-23 16:04:54 +0200 <liskin> it's probably just that when it's someone else display, the distance from my eyes is greater so the same antialiasing looks better
2022-06-23 16:05:00 +0200 <liskin> *else's
2022-06-23 16:05:55 +0200 <liskin> on my own display I can easily tell between subpixel and grayscale antialiasing, because I sit close to it and also look at it for longer periods of time so details stand out
2022-06-23 16:11:28 +0200laymoth[m](~laymothma@2001:470:69fc:105::2:3526)
2022-06-23 17:13:22 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.5)
2022-06-23 17:16:10 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-06-23 18:00:11 +0200RudraveerMandal[(~magphimat@2001:470:69fc:105::2:eb9) (Quit: You have been kicked for being idle)
2022-06-23 18:13:27 +0200benin0(~benin@183.82.30.117) (Quit: The Lounge - https://thelounge.chat)
2022-06-23 18:21:26 +0200 <dminuoso> liskin: One thing I was wondering about, is that my screen is physicall a WQHD display but with a configured resolution of 1080p
2022-06-23 18:22:11 +0200 <dminuoso> In principle there would be the possibility of using all the pixels for antialiasing, right?
2022-06-23 18:25:28 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2022-06-23 18:37:53 +0200alternateved(~alternate@37.120.211.165) (Remote host closed the connection)
2022-06-23 18:49:37 +0200 <liskin> Oh, is it? That probably explains why it felt different
2022-06-23 18:51:00 +0200 <liskin> Wonder why you're running at a non-native resolution then :-)
2022-06-23 20:16:59 +0200allbery_b(~geekosaur@xmonad/geekosaur)
2022-06-23 20:16:59 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2022-06-23 20:17:02 +0200allbery_bgeekosaur
2022-06-23 20:19:32 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds)
2022-06-23 20:22:09 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-06-23 20:36:40 +0200alternateved(~alternate@185.244.214.239)
2022-06-23 21:12:48 +0200diep(~diep@2a01:cb11:2d7:4a00:4202:8c7d:a3d3:256f)
2022-06-23 21:16:34 +0200 <diep> Hi, I just updated xmonad and xmonad-contrib (git branch master), and since I observe border with wrong opacity for some windows like Alacritty, Firefox, Chromium. I use Picom as a compositor. Any idea on what can cause this problem?
2022-06-23 21:17:00 +0200 <geekosaur> we reverted the opacity fix because it broke WindowNavigation
2022-06-23 21:17:12 +0200 <geekosaur> https://github.com/xmonad/xmonad/issues/395
2022-06-23 21:17:34 +0200 <geekosaur> still working on a more correct fix that doesn't break other stuff
2022-06-23 21:18:01 +0200 <geekosaur> (the opacity fix technically does a number of things incorrectly, which may or may not be related to it breaking WN)
2022-06-23 21:20:26 +0200 <diep> Okay, so I'll wait, not really a big deal, and of course WindowNavigation seems more important than some opacity bug on some borders
2022-06-23 21:20:55 +0200 <diep> But I never experienced "window navigation" problem by the way
2022-06-23 21:27:43 +0200 <geekosaur> not everyone does, apparently, but we've had several reports of all-black borders when using WindowNavigation
2022-06-23 21:28:00 +0200 <geekosaur> and when it happens we get a supposedly impossible error code from X11
2022-06-23 21:32:15 +0200 <diep> ok, thx for the info
2022-06-23 21:37:39 +0200diep(~diep@2a01:cb11:2d7:4a00:4202:8c7d:a3d3:256f) (Quit: diep)
2022-06-23 21:45:37 +0200 <alternateved> There are WindowNavigation and Navigation2D modules. Aren't they pretty much similar in functionality?
2022-06-23 21:46:18 +0200 <alternateved> Except for the fact that Navigation2D does a bit more and seems a bit more configurable
2022-06-23 22:06:40 +0200 <geekosaur> WindowNavigation does things like recoloring window borders to show navigation targets and your previous window, plus it provides hooks used by several other modules
2022-06-23 22:06:57 +0200 <geekosaur> and iirc it uses Navigation2D underneath
2022-06-23 22:34:33 +0200ft(~ft@shell.chaostreff-dortmund.de) (Ping timeout: 248 seconds)
2022-06-23 22:35:49 +0200ft(~ft@shell.chaostreff-dortmund.de)
2022-06-23 22:50:23 +0200diep(~diep@2a01:cb11:2d7:4a00:4202:8c7d:a3d3:256f)
2022-06-23 23:04:43 +0200 <liskin> diep: if I was in your place I'd just revert the revert
2022-06-23 23:05:18 +0200 <liskin> (and if I ever update xmonad myself I will be in that position and I will revert becase I don't use windownavigation so the transparency fix is more important for me)
2022-06-23 23:05:45 +0200 <liskin> (and when I say revert obviously I mean locally/in my fork)
2022-06-23 23:06:28 +0200 <diep> yes, good idea after all
2022-06-23 23:08:47 +0200 <diep> since I dont use windownavigation as well
2022-06-23 23:12:45 +0200 <diep> Im trying to add keybinds to switch and move client to screen 1, 2, but without success
2022-06-23 23:12:51 +0200 <diep> I have this https://pastebin.com/AAdDXQPG
2022-06-23 23:13:00 +0200 <diep> when I recompile I get an error
2022-06-23 23:13:11 +0200 <diep> what is wrong?
2022-06-23 23:13:40 +0200 <diep> I want to use right Alt for these keybinds
2022-06-23 23:16:01 +0200 <diep> By screen I mean physical screens
2022-06-23 23:17:28 +0200 <diep> Sorry but I dont know haskell
2022-06-23 23:17:30 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: Lost terminal)
2022-06-23 23:21:58 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-06-23 23:25:10 +0200 <geekosaur> off the top of my head, that looks correct. perhaps the question is where/how you're putting that in your config
2022-06-23 23:26:14 +0200 <geekosaur> (I'm going to be in and out for a bit, today is laundry day)
2022-06-23 23:27:03 +0200 <diep> ok no problem, this is how it's look in the config -> https://github.com/doums/dotfiles/blob/d0a72e81c1e0754cfd97ebf74f96424f2f4a6010/xmonad/xmonad.hs#L…
2022-06-23 23:27:14 +0200 <diep> (commented currently)
2022-06-23 23:28:38 +0200 <diep> How I found out, missing the `++`
2022-06-23 23:36:19 +0200diep(~diep@2a01:cb11:2d7:4a00:4202:8c7d:a3d3:256f) (Quit: diep)