2023/07/19

2023-07-19 00:23:20 +0000ml|(~ml|@user/ml/x-5298235) (Ping timeout: 250 seconds)
2023-07-19 00:36:29 +0000ml|(~ml|@user/ml/x-5298235)
2023-07-19 01:02:25 +0000hightower3(~hightower@213-202-64-66.dsl.iskon.hr)
2023-07-19 01:04:57 +0000hightower2(~hightower@141-136-175-55.dsl.iskon.hr) (Ping timeout: 245 seconds)
2023-07-19 01:47:38 +0000obimod(~weechat@user/obimod) (Ping timeout: 240 seconds)
2023-07-19 02:27:34 +0000td_(~td@i53870919.versanet.de) (Ping timeout: 272 seconds)
2023-07-19 02:28:46 +0000td_(~td@i5387092E.versanet.de)
2023-07-19 02:42:14 +0000terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2023-07-19 02:45:18 +0000terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2023-07-19 02:48:46 +0000thunderrd(~thunderrd@183.182.111.104) (Ping timeout: 245 seconds)
2023-07-19 02:52:33 +0000 <absta[m]> Oh do you think Wayland protocol of monolithic compositor is inevitable?
2023-07-19 04:15:26 +0000geekosaur[c](sid609282@xmonad/geekosaur) (Ping timeout: 246 seconds)
2023-07-19 04:19:22 +0000geekosaur[c](sid609282@xmonad/geekosaur)
2023-07-19 06:09:23 +0000 <geekosaur> yes
2023-07-19 06:09:26 +0000 <geekosaur> and necessary
2023-07-19 06:10:19 +0000 <geekosaur> X11's compositor setup is an ugly hack that will always perform horribly and be weirdly unstable
2023-07-19 06:11:06 +0000 <geekosaur> "the compositor is the display server" is the same thing as "the display server is the compositor" which is how it should have been to begin with
2023-07-19 06:12:00 +0000 <geekosaur> but with X11's 1980s architecture it isn't possible
2023-07-19 06:15:46 +0000mncheck(~mncheck@193.224.205.254)
2023-07-19 06:16:02 +0000 <geekosaur> the only real problem with wayland is it'll take 5-10 years to mature
2023-07-19 06:17:16 +0000 <geekosaur> (well, the real real problem with it is monolithic gnome being rammed down everyone's throats, but that's rh/gnome, not something required by wayland)
2023-07-19 06:47:50 +0000 <geekosaur> I suspect what will happen is gnome and maybe kde will use their own monoliths and everyone else will standardize on wlroots or similar; in fact it's already happening
2023-07-19 06:50:10 +0000 <geekosaur> (and indeed I just checked and KDE seems to be moving to wlroots)
2023-07-19 06:51:28 +0000 <geekosaur> so in the end wlroots is likely to become a more traditional display server, with the compositor baked in because it needs to be tight up with the low level display drivers to work well
2023-07-19 06:52:19 +0000 <geekosaur> and KDE, Sway, Enlightenment, and presumably some form of xmonad among others will use it
2023-07-19 07:00:47 +0000 <geekosaur> what I hope is that standardization will see something usable in manageHooks to come back; currently gnome doesn't use it so nobody implements it
2023-07-19 08:56:38 +0000ft(~ft@p3e9bc856.dip0.t-ipconnect.de) (Quit: leaving)
2023-07-19 10:46:05 +0000 <absta[m]> I thought gnome went that way because of Wayland, not the other way around ;P
2023-07-19 10:47:08 +0000 <absta[m]> It makes sense how compositor and display server is tied together, but I am yet to see why window management and various functionalities like taskbar would be tied up to the compositor. Wish wlroots would become a proper compositor!
2023-07-19 11:10:07 +0000tv(~tv@user/tv) (Quit: derp)
2023-07-19 11:13:36 +0000tv(~tv@user/tv)
2023-07-19 11:30:22 +0000obimod(~weechat@user/obimod)
2023-07-19 12:11:30 +0000tv1(~tv@user/tv)
2023-07-19 12:11:32 +0000tv(~tv@user/tv) (Ping timeout: 240 seconds)
2023-07-19 14:04:47 +0000 <geekosaur> I thought it was
2023-07-19 14:05:11 +0000 <geekosaur> wlroots is the compositor component of sway but has been adopted by a number of other wayland window managers
2023-07-19 14:05:26 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2023-07-19 14:06:22 +0000 <geekosaur> window management doesn't need to be directly tied to the compositor; it wants better integration than X11 offers but that's because it's not part of the window system core / the display driver
2023-07-19 15:16:10 +0000gar[m](~randyorto@2001:470:69fc:105::3:85fa)
2023-07-19 15:19:58 +0000 <gar[m]> Can I open certain sites on opening browser on a particular workspace and login to them using selenium with xmonad
2023-07-19 15:21:34 +0000 <geekosaur> I would expect yes, although you would need to do some work
2023-07-19 15:22:16 +0000 <geekosaur> https://hackage.haskell.org/package/webdriver may be of interest
2023-07-19 16:10:12 +0000liskin[m](~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection)
2023-07-19 16:37:32 +0000unclechu(~unclechu@2001:470:69fc:105::354) (Remote host closed the connection)
2023-07-19 17:30:33 +0000jeeeun(~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat)
2023-07-19 17:35:58 +0000jeeeun(~jeeeun@78.40.148.178)
2023-07-19 18:02:43 +0000scrungus(~scrungus@70.24.87.181)
2023-07-19 18:03:44 +0000 <scrungus> Does anyone here use window swallowing? I have this issue where when I launch an application through dmenu it swallows whatever terminal window happened to be focused
2023-07-19 18:04:00 +0000liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-07-19 18:04:14 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2023-07-19 18:07:46 +0000scrungus(~scrungus@70.24.87.181) (Quit: WeeChat 4.0.2)
2023-07-19 18:12:54 +0000scrungus(~scrungus@70.24.87.181)
2023-07-19 18:17:46 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2023-07-19 18:17:46 +0000allbery_b(~geekosaur@xmonad/geekosaur)
2023-07-19 18:17:49 +0000allbery_bgeekosaur
2023-07-19 18:19:17 +0000xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 246 seconds)
2023-07-19 18:36:39 +0000scrungus(~scrungus@70.24.87.181) (Quit: WeeChat 4.0.2)
2023-07-19 18:41:28 +0000xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-07-19 18:41:28 +0000xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-07-19 18:41:28 +0000xmonadtrack(~xmonadtra@user/geekosaur/bot/xmonadtrack)
2023-07-19 21:19:40 +0000ft(~ft@p3e9bc856.dip0.t-ipconnect.de)
2023-07-19 22:03:32 +0000sagax(~sagax_nb@user/sagax)
2023-07-19 22:22:56 +0000mncheck(~mncheck@193.224.205.254) (Ping timeout: 245 seconds)
2023-07-19 23:24:36 +0000ft(~ft@p3e9bc856.dip0.t-ipconnect.de) (Ping timeout: 245 seconds)
2023-07-19 23:31:23 +0000ft(~ft@p3e9bcb94.dip0.t-ipconnect.de)