| 2022-03-18 00:10:32 +0000 | yauhsien | (~Yau-Hsien@61-231-56-96.dynamic-ip.hinet.net) |
| 2022-03-18 00:18:04 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) |
| 2022-03-18 00:43:32 +0000 | SignalGarden | (~ash@user/SignalWalker) (Ping timeout: 250 seconds) |
| 2022-03-18 00:45:37 +0000 | n8nl | (~n8nl@c-24-61-77-34.hsd1.ma.comcast.net) (Ping timeout: 240 seconds) |
| 2022-03-18 00:50:31 +0000 | n8nl | (~n8nl@c-24-61-77-34.hsd1.ma.comcast.net) |
| 2022-03-18 00:55:53 +0000 | thunderrd | (~thunderrd@183.182.111.123) (Remote host closed the connection) |
| 2022-03-18 01:05:46 +0000 | SignalGarden | (~ash@user/SignalWalker) |
| 2022-03-18 01:31:32 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) (Ping timeout: 240 seconds) |
| 2022-03-18 01:32:12 +0000 | chomwitt | (~chomwitt@2a02:587:dc19:ca00:a7f3:60c8:c144:5351) (Ping timeout: 240 seconds) |
| 2022-03-18 01:39:00 +0000 | SignalGarden | (~ash@user/SignalWalker) (Ping timeout: 250 seconds) |
| 2022-03-18 01:39:24 +0000 | SignalGarden | (~ash@user/SignalWalker) |
| 2022-03-18 01:42:54 +0000 | n8nl | (~n8nl@c-24-61-77-34.hsd1.ma.comcast.net) (Ping timeout: 250 seconds) |
| 2022-03-18 02:39:15 +0000 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-03-18 02:48:47 +0000 | SignalGarden | (~ash@user/SignalWalker) (Quit: WeeChat 3.4.1) |
| 2022-03-18 03:04:37 +0000 | banc | (~banc@217.138.195.27) (Ping timeout: 240 seconds) |
| 2022-03-18 03:22:54 +0000 | banc | (~banc@217.138.195.27) |
| 2022-03-18 03:24:05 +0000 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
| 2022-03-18 03:24:29 +0000 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2022-03-18 03:31:15 +0000 | <abhixec> | is there a way to get hidpi working on xmonad sanely as in not having to constantly restart x every time I connect/disconnect to a hidpi monitor. Currently the only way to make it look sane is setting xft.dpi to 192 but it becomes ugly when I want to go back to using my laptop then I need to revert it to 96 and startx again |
| 2022-03-18 03:31:27 +0000 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-03-18 03:51:16 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) |
| 2022-03-18 04:01:44 +0000 | amenonsen | (~amenonsen@pitta.toroid.org) (Remote host closed the connection) |
| 2022-03-18 04:09:50 +0000 | amenonsen | (~amenonsen@pitta.toroid.org) |
| 2022-03-18 04:42:12 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) (Ping timeout: 240 seconds) |
| 2022-03-18 05:11:38 +0000 | bfrk | (~Thunderbi@2001:9e8:34d:3e00:6718:858b:daf3:34ec) |
| 2022-03-18 05:13:30 +0000 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Ping timeout: 250 seconds) |
| 2022-03-18 05:21:57 +0000 | bfrk | (~Thunderbi@2001:9e8:34d:3e00:6718:858b:daf3:34ec) (Ping timeout: 240 seconds) |
| 2022-03-18 05:31:49 +0000 | thunderrd | (~thunderrd@183.182.111.150) |
| 2022-03-18 05:50:14 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection) |
| 2022-03-18 05:52:05 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-03-18 06:15:59 +0000 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 256 seconds) |
| 2022-03-18 06:18:08 +0000 | chomwitt | (~chomwitt@2a02:587:dc19:ca00:67fe:b14c:d83a:53d8) |
| 2022-03-18 06:39:14 +0000 | haasn | (~nand@haasn.dev) (*.net *.split) |
| 2022-03-18 06:44:34 +0000 | haasn | (~nand@haasn.dev) |
| 2022-03-18 07:18:55 +0000 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Remote host closed the connection) |
| 2022-03-18 08:01:44 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2022-03-18 08:26:00 +0000 | chomwitt | (~chomwitt@2a02:587:dc19:ca00:67fe:b14c:d83a:53d8) (Remote host closed the connection) |
| 2022-03-18 08:37:15 +0000 | bfrk | (~Thunderbi@2001:9e8:34d:3e00:6718:858b:daf3:34ec) |
| 2022-03-18 08:48:14 +0000 | mc47 | (~mc47@xmonad/TheMC47) |
| 2022-03-18 09:26:39 +0000 | jeeeun | (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat) |
| 2022-03-18 09:27:11 +0000 | jeeeun | (~jeeeun@78.40.148.178) |
| 2022-03-18 09:38:54 +0000 | korner[m] | (~mistrkorn@2001:470:69fc:105::68e9) |
| 2022-03-18 09:40:28 +0000 | <korner[m]> | hey how is cursor capture on xmonad? finally found a good excuse to finally check xmonad out because old games are very very broken on my wayland setup |
| 2022-03-18 10:36:19 +0000 | <tomjaguarpaw> | liskin: https://paste.tomsmeding.com/ebZv5he0 |
| 2022-03-18 10:37:29 +0000 | <tomjaguarpaw> | This is what happens when I have my X in external-only mode, and then unplug the external screen without having changed to the internal screen, but then subsequently use xrandr to change to the internal screen (blind, because I have not screen at that point) |
| 2022-03-18 10:37:41 +0000 | <tomjaguarpaw> | X seems to think that I have two screens, when I only have one |
| 2022-03-18 10:39:15 +0000 | <tomjaguarpaw> | If I plug the external screen back in, then use xrandr to change to (only) internal screen that works fine (and I can unplug the external safely) |
| 2022-03-18 10:39:43 +0000 | <tomjaguarpaw> | It would be great to know how to make X forget about the external screen, without having to plug it in first! |
| 2022-03-18 10:40:06 +0000 | <tomjaguarpaw> | I'm not sure this is related to XMonad at all, ..., but if anyone knows how I should deal with it that would be very helpful |
| 2022-03-18 10:45:29 +0000 | <geekosaur> | the driver should be detecting that automatically and sending xmonad and other programs an RRChangeNotify event |
| 2022-03-18 10:55:43 +0000 | <tomjaguarpaw> | And xrandr doesn't even know about the change! Does that means it's a driver bug? |
| 2022-03-18 10:57:20 +0000 | <geekosaur> | yes |
| 2022-03-18 10:57:52 +0000 | <geekosaur> | only the driver has the direct access needed to recognize monitor connection/disconnection |
| 2022-03-18 10:58:11 +0000 | <geekosaur> | I would be curious to see if the bug is still there if you're not overlapping them, though |
| 2022-03-18 10:58:27 +0000 | <korner[m]> | that is X thing that it doesnt forget monitors after they have been unplugged, supposedly its feature so you need some automized way to check for it |
| 2022-03-18 10:58:34 +0000 | <geekosaur> | I know some (possibly many) drivers break if monitors aren't contiguous |
| 2022-03-18 10:58:44 +0000 | <tomjaguarpaw> | I'm not overlapping them |
| 2022-03-18 10:59:12 +0000 | <geekosaur> | isn'tr one portrait and one landscape but with the same origin? |
| 2022-03-18 10:59:23 +0000 | <tomjaguarpaw> | I generally only have one on the other enabled. If I have both enabled then I have the internal one below the external one. |
| 2022-03-18 10:59:37 +0000 | <geekosaur> | ah |
| 2022-03-18 10:59:47 +0000 | <tomjaguarpaw> | Not sure how X keeps track of these things, but I never display the same thing on separate screens. |
| 2022-03-18 11:00:10 +0000 | <tomjaguarpaw> | It's possible they "became" overlapped when I tried to switch to the internal monitor. |
| 2022-03-18 11:00:33 +0000 | <geekosaur> | korner[m], I don't understand your question. cursor capture is independent of the window manager, and is usually implemented via grabs so it overrides the window manager |
| 2022-03-18 11:01:01 +0000 | <tomjaguarpaw> | But it's hard to debug this because when I unplug the external and I want to activate the internal I have nothing on my screen! All I can do is Ctrl-R in the terminal and hope I hit my xrandr shell script! |
| 2022-03-18 11:01:11 +0000 | <geekosaur> | the screen info you pulled up the other day for me showed them as I described |
| 2022-03-18 11:01:42 +0000 | <tomjaguarpaw> | Yeah, probably an artefact of how I recovered from the situation. |
| 2022-03-18 11:02:11 +0000 | <geekosaur> | also you could consider binding a key to run your shell script (or multiple if you need torun it in different ways) so you don't have to guess |
| 2022-03-18 11:02:51 +0000 | <tomjaguarpaw> | Yes, I think that's a good idea |
| 2022-03-18 11:03:39 +0000 | <geekosaur> | back in the old days I used to have a keyy bound to kill xcompmgr when it went crazy, and likewise I couldn't see what was really on screen |
| 2022-03-18 11:06:53 +0000 | <korner[m]> | speaking of compositing, is there any way i can prevent screen tear without compositors? i am not particularly interested in them and just locking entire xorg to 60 frames would do |
| 2022-03-18 11:07:31 +0000 | <geekosaur> | some video drivers have options for it |
| 2022-03-18 11:07:46 +0000 | <korner[m]> | regarding that cursor capture question, can safely ignore |
| 2022-03-18 11:07:56 +0000 | <korner[m]> | i use only intel ones which is i915 i think? |
| 2022-03-18 11:19:45 +0000 | <geekosaur> | the intel one covers most intel chipsets |
| 2022-03-18 11:20:10 +0000 | <geekosaur> | if you turn on verbose boot you'll see it prints out 3-4lines about all the chipsets it covers |
| 2022-03-18 11:36:38 +0000 | yauhsien | (~Yau-Hsien@61-231-56-96.dynamic-ip.hinet.net) (Quit: Leaving) |
| 2022-03-18 11:53:16 +0000 | <korner[m]> | i have modern UHD chipset so i am 100% in the clear, i will see later when i get config together if it works with those xorg options |
| 2022-03-18 11:55:38 +0000 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.3) |
| 2022-03-18 11:57:07 +0000 | cfricke | (~cfricke@user/cfricke) |
| 2022-03-18 12:19:51 +0000 | <Solid> | tomjaguarpaw: I didn't completely follow the whole conversation but to me it sounds like you want different monitor configurations ala autorandr instead of self-written shell scripts |
| 2022-03-18 12:20:02 +0000 | <Solid> | (well, I guess one would still need to bind `autorandr --change` to a key in case things don't get recognised) |
| 2022-03-18 12:32:44 +0000 | cfricke | (~cfricke@user/cfricke) (Ping timeout: 268 seconds) |
| 2022-03-18 12:47:26 +0000 | bfrk | (~Thunderbi@2001:9e8:34d:3e00:6718:858b:daf3:34ec) (Ping timeout: 245 seconds) |
| 2022-03-18 13:37:20 +0000 | SignalGarden | (~ash@user/SignalWalker) |
| 2022-03-18 13:55:45 +0000 | geekosaur | (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
| 2022-03-18 13:57:15 +0000 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-03-18 14:17:41 +0000 | twiclo1 | (~twiclo@2604:7b80:2000:1069:52fc:cedd:fbeb:10c) |
| 2022-03-18 14:35:12 +0000 | SignalGarden | (~ash@user/SignalWalker) (Quit: WeeChat 3.4.1) |
| 2022-03-18 14:53:34 +0000 | SignalGarden | (~ash@user/SignalWalker) |
| 2022-03-18 15:14:53 +0000 | <liskin> | Hm, the paste completely freezes chrome on Android, weird |
| 2022-03-18 15:16:49 +0000 | <liskin> | Stackage 19 with new xmonad is out btw :-) |
| 2022-03-18 15:19:30 +0000 | <Solid> | oh awesome |
| 2022-03-18 15:19:49 +0000 | <Solid> | oh shit 9.0.2 as well |
| 2022-03-18 15:28:32 +0000 | <geekosaur> | yay, maybe we'llfinally see some other distros update too |
| 2022-03-18 15:29:49 +0000 | <Solid> | we'll probably at at least see nix update now |
| 2022-03-18 15:30:22 +0000 | <Solid> | arch has been on ghc 9 for a while (even on 9.0.1, which was quite broken), so unlikely there :/ |
| 2022-03-18 16:03:50 +0000 | SignalGarden | (~ash@user/SignalWalker) (Ping timeout: 252 seconds) |
| 2022-03-18 16:14:28 +0000 | SignalGarden | (~ash@user/SignalWalker) |
| 2022-03-18 16:14:35 +0000 | seschwar | (~seschwar@user/seschwar) |
| 2022-03-18 16:30:54 +0000 | Ash[m] | (~signal-wa@2001:470:69fc:105::1:2318) |
| 2022-03-18 16:31:44 +0000 | SignalGarden | (~ash@user/SignalWalker) (WeeChat 3.4.1) |
| 2022-03-18 16:40:05 +0000 | bfrk | (~Thunderbi@i59F7ABB6.versanet.de) |
| 2022-03-18 17:04:54 +0000 | ml| | (~ml|@user/ml/x-5298235) (Ping timeout: 252 seconds) |
| 2022-03-18 17:18:21 +0000 | yauhsien | (~Yau-Hsien@61-231-56-96.dynamic-ip.hinet.net) |
| 2022-03-18 17:18:36 +0000 | bfrk | (~Thunderbi@i59F7ABB6.versanet.de) (Ping timeout: 240 seconds) |
| 2022-03-18 17:36:55 +0000 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
| 2022-03-18 17:53:30 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) |
| 2022-03-18 18:34:02 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) (Ping timeout: 240 seconds) |
| 2022-03-18 20:00:21 +0000 | bfrk | (~Thunderbi@i59F7ABB6.versanet.de) |
| 2022-03-18 20:05:52 +0000 | MrElendig | (~Urist@archlinux/op/MrElendig) (Quit: invading russia) |
| 2022-03-18 20:07:56 +0000 | MrElendig | (~Urist@archlinux/op/MrElendig) |
| 2022-03-18 20:18:09 +0000 | Guest81 | (~Guest81@196.235.125.240) |
| 2022-03-18 20:19:53 +0000 | jimr | (~jimr@2603-7080-7640-b000-0000-0000-0000-0003.res6.spectrum.com) |
| 2022-03-18 20:22:35 +0000 | mvk | (~mvk@2607:fea8:5cc3:7e00::45ee) |
| 2022-03-18 20:23:59 +0000 | bfrk | (~Thunderbi@i59F7ABB6.versanet.de) (Read error: No route to host) |
| 2022-03-18 20:24:46 +0000 | bfrk | (~Thunderbi@2001:9e8:34d:3e00:6718:858b:daf3:34ec) |
| 2022-03-18 20:28:13 +0000 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
| 2022-03-18 20:31:14 +0000 | Guest81 | (~Guest81@196.235.125.240) (Quit: Client closed) |
| 2022-03-18 20:34:58 +0000 | ml| | (~ml|@user/ml/x-5298235) |
| 2022-03-18 20:59:48 +0000 | jimr | (~jimr@2603-7080-7640-b000-0000-0000-0000-0003.res6.spectrum.com) (Quit: Leaving) |
| 2022-03-18 21:02:02 +0000 | jimr | (~jimr@2603-7080-7640-b000-0000-0000-0000-0003.res6.spectrum.com) |
| 2022-03-18 21:20:50 +0000 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) |
| 2022-03-18 21:31:10 +0000 | abhixec | (~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving) |
| 2022-03-18 21:43:49 +0000 | jimr | (~jimr@2603-7080-7640-b000-0000-0000-0000-0003.res6.spectrum.com) (Quit: Leaving) |
| 2022-03-18 22:31:46 +0000 | bfrk | (~Thunderbi@2001:9e8:34d:3e00:6718:858b:daf3:34ec) (Ping timeout: 250 seconds) |
| 2022-03-18 22:33:24 +0000 | twiclo1 | (~twiclo@2604:7b80:2000:1069:52fc:cedd:fbeb:10c) (Ping timeout: 240 seconds) |
| 2022-03-18 23:48:26 +0000 | twiclo1 | (~twiclo@mail.twil.cx) |
| 2022-03-18 23:56:31 +0000 | seschwar | (~seschwar@user/seschwar) (Quit: :wq) |