Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→ 184,913 events total
2023-09-23 21:13:29 <haskellbridge> <s​cholablade> I have both 9.2.8 and 9.4.7
2023-09-23 21:13:41 <geekosaur> yeh, but 9.2.8 is `set` apparently
2023-09-23 21:13:52 <geekosaur> because that's what lts-20.26 wants
2023-09-23 21:15:26 <haskellbridge> <s​cholablade> Seems to work!
2023-09-23 21:15:42 <haskellbridge> <s​cholablade> Thanks for the help
2023-09-23 21:16:01 <geekosaur> I have a bunch of ghc versions installed including a 9.8 prerelease, but 9.6.2 is default / "set"
2023-09-23 21:16:38 <haskellbridge> <s​cholablade> I have made it so that 9.2.8 is "set"
2023-09-23 21:39:16 sagax joins (~sagax_nb@user/sagax)
2023-09-23 22:26:07 × chomwitt quits (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)
2023-09-24 00:08:56 fabz joins (~fabz@2804:7f0:b401:7ce8:7d06:5c29:20eb:f99b)
2023-09-24 00:09:32 × fabz quits (~fabz@2804:7f0:b401:7ce8:7d06:5c29:20eb:f99b) (Client Quit)
2023-09-24 02:13:19 × td_ quits (~td@i5387093D.versanet.de) (Ping timeout: 258 seconds)
2023-09-24 02:15:16 td_ joins (~td@i5387092C.versanet.de)
2023-09-24 03:14:47 × tremon quits (~tremon@83.80.159.219) (Quit: getting boxed in)
2023-09-24 03:26:34 × srk quits (~sorki@user/srk) (Remote host closed the connection)
2023-09-24 03:26:54 srk joins (~sorki@user/srk)
2023-09-24 07:23:49 × jsoo quits (~znc@irc.refl.club) (Ping timeout: 245 seconds)
2023-09-24 07:30:41 jsoo joins (~znc@irc.refl.club)
2023-09-24 07:32:33 thyriaen joins (~thyriaen@2a01:aea0:dd4:7157:6245:cbff:fe9f:48b1)
2023-09-24 09:19:12 × sagax quits (~sagax_nb@user/sagax) (Ping timeout: 258 seconds)
2023-09-24 10:48:56 chomwitt joins (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1)
2023-09-24 12:16:21 × hightower2 quits (~hightower@85.94.71.188) (Ping timeout: 244 seconds)
2023-09-24 12:40:41 × de-vri-es quits (~de-vri-es@voyager.de-vri.es) (Ping timeout: 246 seconds)
2023-09-24 12:43:38 hightower2 joins (~hightower@141-136-211-208.dsl.iskon.hr)
2023-09-24 12:54:00 de-vri-es joins (~de-vri-es@voyager.de-vri.es)
2023-09-24 12:57:43 × vanvik quits (~vanvik@78.156.11.181) (Quit: Later)
2023-09-24 12:58:05 vanvik joins (~vanvik@78.156.11.181)
2023-09-24 14:03:26 lb9di is now known as pantsu
2023-09-24 14:50:55 × noze`` quits (~user@2001:41d0:a:21f1::1) (Read error: Connection reset by peer)
2023-09-24 15:39:09 ircbrowse_tom joins (~ircbrowse@static.162.49.55.162.clients.your-server.de)
2023-09-24 15:39:11 Server sets mode +cnt
2023-09-24 17:29:19 × thyriaen quits (~thyriaen@2a01:aea0:dd4:7157:6245:cbff:fe9f:48b1) (Remote host closed the connection)
2023-09-24 22:00:05 × vanvik quits (~vanvik@78.156.11.181) (Ping timeout: 240 seconds)
2023-09-24 22:00:18 vanvik joins (~vanvik@78.156.11.181)
2023-09-24 22:05:21 × scardinal quits (~supreme@87.61.100.169) (Ping timeout: 244 seconds)
2023-09-24 22:12:05 scardinal joins (~supreme@87.61.100.169)
2023-09-24 23:22:31 × chomwitt quits (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)
2023-09-25 00:22:25 <haskellbridge> <R​en> I was hoping someone could help me understand XMonad's behavior. I've been playing around with making my own GTK app to have as a desktop background so it has the window hint GDK_WINDOW_TYPE_HINT_DESKTOP, and the docks XConfig correctly ignores it letting it sit in the background, but by doing so it puts a complete stop to mouse-over switching screens. Without my desktop backgrou
2023-09-25 00:22:25 <haskellbridge> <clipped message>
2023-09-25 00:22:26 <haskellbridge> <R​en> nd app running, the screen focus switches as I move my mouse between monitors even if those screen are devoid of any windows to actually focus on. How can I maintain this feature while still having a desktop app? Is it even possible?
2023-09-25 00:23:27 <geekosaur> no. X11 limitation
2023-09-25 00:23:56 <geekosaur> well, might work if your program ignores Xinerama/XRandR and covers the entire root window
2023-09-25 00:24:27 <geekosaur> but I suspect not because the root window is treated specially by XRandR
2023-09-25 00:26:09 <haskellbridge> <R​en> That's too bad, and I've gotten so used to the convenience too. This is my first time using GTK and trying to dive into this stuff in general, so I wouldn't know how to try out that root window thing, but I'll keep it in mind as I learn
2023-09-25 00:26:41 <haskellbridge> <R​en> Thanks for the quick answer
2023-09-25 00:26:55 <geekosaur> an alternative might be to draw directly into the root window instead of creating your own desktop window
2023-09-25 01:00:32 <haskellbridge> <R​en> I certainly don't know how to do that at the moment, would that even maintain the interactivity of the program?
2023-09-25 01:20:33 <geekosaur> no
2023-09-25 01:37:06 <haskellbridge> <R​en> Yeah, I just experimented some with xwinwrap, I'll wager a guess that the X11 limitation involves the window capturing input since not passing -ni (no input) to xwinwrap also puts an end to automatic screen switching
2023-09-25 01:38:18 <geekosaur> it's a little more complex than that
2023-09-25 01:38:44 <geekosaur> multiple screens in X11 are a big hack involving the root window, so only the root window is actually aware of multiple screens
2023-09-25 01:43:10 <haskellbridge> <R​en> So, mousing over the root window, and information on what screen it is can be gathered, but any other window has no idea what screen it is on?
2023-09-25 01:48:08 <geekosaur> essentially, yes
2023-09-25 01:48:14 <geekosaur> that's a large part of the hack
2023-09-25 01:49:18 <geekosaur> all the monitors are carved out of the root window; normal windows generally stick to a monitor. and mouse position is reported relative to the window's upper left corner, so only the root which spans all monitors knows the mouse's true position
2023-09-25 01:49:54 <geekosaur> which is why I suggested trying to create a window spanning the entire root; hopefully it'll work the same way. but gtk will fight it
2023-09-25 01:58:30 <haskellbridge> <R​en> Well just going with what I know, making the window span both my screens results is functionally the same result as just having it on my first monitor, so I think the screen it knows about is the one where it's origin in, even though it spans both monitors. I suppose if one could send a message to XMonad and ask to switch to n screen, It could be possible to recreate the original
2023-09-25 01:58:30 <haskellbridge> <clipped message>
2023-09-25 01:58:31 <haskellbridge> <R​en> behavior, since the gdk library has enough info to build a full model of my screens
2023-09-25 01:59:46 <haskellbridge> <R​en> But that is also probably not so simple, if at all possible since I doubt it is getting mouse events a lot since most of the time, windows are on top of it
2023-09-25 02:12:21 × td_ quits (~td@i5387092C.versanet.de) (Ping timeout: 258 seconds)
2023-09-25 02:13:59 td_ joins (~td@i53870932.versanet.de)
2023-09-25 05:34:03 chomwitt joins (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1)
2023-09-25 07:11:07 × chomwitt quits (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)
2023-09-25 07:17:25 chomwitt joins (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1)
2023-09-25 07:43:33 × hightower2 quits (~hightower@141-136-211-208.dsl.iskon.hr) (Ping timeout: 258 seconds)
2023-09-25 08:10:37 × matijja quits (~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in)
2023-09-25 08:11:29 matijja joins (~matijja@193.77.181.201)
2023-09-25 08:18:13 hightower2 joins (~hightower@85.94.71.188)
2023-09-25 08:24:50 cfricke joins (~cfricke@user/cfricke)
2023-09-25 08:56:35 × cfricke quits (~cfricke@user/cfricke) (Ping timeout: 240 seconds)
2023-09-25 09:02:05 cfricke joins (~cfricke@user/cfricke)
2023-09-25 09:21:48 × chomwitt quits (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1) (Ping timeout: 240 seconds)
2023-09-25 10:09:30 × ft quits (~ft@p3e9bc680.dip0.t-ipconnect.de) (Quit: leaving)
2023-09-25 10:56:13 srk- joins (~sorki@user/srk)
2023-09-25 10:58:47 srk| joins (~sorki@user/srk)
2023-09-25 10:59:19 × srk quits (~sorki@user/srk) (Ping timeout: 244 seconds)
2023-09-25 11:01:55 srk| is now known as srk
2023-09-25 11:02:29 × srk- quits (~sorki@user/srk) (Ping timeout: 255 seconds)
2023-09-25 11:23:15 raghavgururajan_ joins (ea769b8000@2604:bf00:561:2000::242)
2023-09-25 11:23:20 zoglesby_ joins (f0f8ca1525@2604:bf00:561:2000::64)
2023-09-25 11:24:00 samhh__ joins (7569f027cf@2604:bf00:561:2000::e4)
2023-09-25 11:25:57 chomwitt joins (~chomwitt@2a02:587:7a2f:d000:1ac0:4dff:fedb:a3f1)
2023-09-25 11:27:55 alethkit_ joins (23bd17ddc6@sourcehut/user/alethkit)
2023-09-25 11:30:55 × jludwig quits (~justin@li657-110.members.linode.com) (*.net *.split)
2023-09-25 11:30:56 × alethkit quits (23bd17ddc6@sourcehut/user/alethkit) (*.net *.split)
2023-09-25 11:30:57 × samhh quits (7569f027cf@2604:bf00:561:2000::e4) (*.net *.split)
2023-09-25 11:30:58 × zoglesby quits (f0f8ca1525@user/zoglesby) (*.net *.split)
2023-09-25 11:30:58 × raghavgururajan quits (ea769b8000@user/raghavgururajan) (*.net *.split)
2023-09-25 11:30:58 × B-J quits (~BenziJuni@88-149-64-112.du.xdsl.is) (*.net *.split)
2023-09-25 11:31:03 alethkit_ is now known as alethkit
2023-09-25 11:31:06 zoglesby_ is now known as zoglesby
2023-09-25 11:31:19 × alethkit quits (23bd17ddc6@sourcehut/user/alethkit) (Read error: Connection reset by peer)
2023-09-25 11:31:19 × samhh__ quits (7569f027cf@2604:bf00:561:2000::e4) (Write error: Connection reset by peer)
2023-09-25 11:31:19 × zoglesby quits (f0f8ca1525@2604:bf00:561:2000::64) (Write error: Connection reset by peer)
2023-09-25 11:31:21 × raghavgururajan_ quits (ea769b8000@2604:bf00:561:2000::242) (Write error: Connection reset by peer)
2023-09-25 11:31:29 zoglesby joins (f0f8ca1525@2604:bf00:561:2000::64)
2023-09-25 11:31:30 raghavgururajan joins (ea769b8000@2604:bf00:561:2000::242)
2023-09-25 11:31:39 × raghavgururajan quits (ea769b8000@2604:bf00:561:2000::242) (Changing host)
2023-09-25 11:31:39 raghavgururajan joins (ea769b8000@user/raghavgururajan)

All times are in UTC.