Logs on 2023-07-19 (liberachat/#xmonad)
| 00:23:20 | × | ml| quits (~ml|@user/ml/x-5298235) (Ping timeout: 250 seconds) |
| 00:36:29 | → | ml| joins (~ml|@user/ml/x-5298235) |
| 01:02:25 | → | hightower3 joins (~hightower@213-202-64-66.dsl.iskon.hr) |
| 01:04:57 | × | hightower2 quits (~hightower@141-136-175-55.dsl.iskon.hr) (Ping timeout: 245 seconds) |
| 01:47:38 | × | obimod quits (~weechat@user/obimod) (Ping timeout: 240 seconds) |
| 02:27:34 | × | td_ quits (~td@i53870919.versanet.de) (Ping timeout: 272 seconds) |
| 02:28:46 | → | td_ joins (~td@i5387092E.versanet.de) |
| 02:42:14 | × | terrorjack quits (~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat) |
| 02:45:18 | → | terrorjack joins (~terrorjac@2a01:4f8:c17:87f8::) |
| 02:48:46 | × | thunderrd quits (~thunderrd@183.182.111.104) (Ping timeout: 245 seconds) |
| 02:52:33 | <absta[m]> | Oh do you think Wayland protocol of monolithic compositor is inevitable? |
| 04:15:26 | × | geekosaur[c] quits (sid609282@xmonad/geekosaur) (Ping timeout: 246 seconds) |
| 04:19:22 | → | geekosaur[c] joins (sid609282@xmonad/geekosaur) |
| 06:09:23 | <geekosaur> | yes |
| 06:09:26 | <geekosaur> | and necessary |
| 06:10:19 | <geekosaur> | X11's compositor setup is an ugly hack that will always perform horribly and be weirdly unstable |
| 06:11:06 | <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 |
| 06:12:00 | <geekosaur> | but with X11's 1980s architecture it isn't possible |
| 06:15:46 | → | mncheck joins (~mncheck@193.224.205.254) |
| 06:16:02 | <geekosaur> | the only real problem with wayland is it'll take 5-10 years to mature |
| 06:17:16 | <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) |
| 06:47:50 | <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 |
| 06:50:10 | <geekosaur> | (and indeed I just checked and KDE seems to be moving to wlroots) |
| 06:51:28 | <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 |
| 06:52:19 | <geekosaur> | and KDE, Sway, Enlightenment, and presumably some form of xmonad among others will use it |
| 07:00:47 | <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 |
| 08:56:38 | × | ft quits (~ft@p3e9bc856.dip0.t-ipconnect.de) (Quit: leaving) |
| 10:46:05 | <absta[m]> | I thought gnome went that way because of Wayland, not the other way around ;P |
| 10:47:08 | <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! |
| 11:10:07 | × | tv quits (~tv@user/tv) (Quit: derp) |
| 11:13:36 | → | tv joins (~tv@user/tv) |
| 11:30:22 | → | obimod joins (~weechat@user/obimod) |
| 12:11:30 | → | tv1 joins (~tv@user/tv) |
| 12:11:32 | × | tv quits (~tv@user/tv) (Ping timeout: 240 seconds) |
| 14:04:47 | <geekosaur> | I thought it was |
| 14:05:11 | <geekosaur> | wlroots is the compositor component of sway but has been adopted by a number of other wayland window managers |
| 14:05:26 | → | unclechu joins (~unclechu@2001:470:69fc:105::354) |
| 14:06:22 | <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 |
| 15:16:10 | → | gar[m] joins (~randyorto@2001:470:69fc:105::3:85fa) |
| 15:19:58 | <gar[m]> | Can I open certain sites on opening browser on a particular workspace and login to them using selenium with xmonad |
| 15:21:34 | <geekosaur> | I would expect yes, although you would need to do some work |
| 15:22:16 | <geekosaur> | https://hackage.haskell.org/package/webdriver may be of interest |
| 16:10:12 | × | liskin[m] quits (~liskinmat@2001:470:69fc:105::768) (Remote host closed the connection) |
| 16:37:32 | × | unclechu quits (~unclechu@2001:470:69fc:105::354) (Remote host closed the connection) |
| 17:30:33 | × | jeeeun quits (~jeeeun@78.40.148.178) (Quit: The Lounge - https://thelounge.chat) |
| 17:35:58 | → | jeeeun joins (~jeeeun@78.40.148.178) |
| 18:02:43 | → | scrungus joins (~scrungus@70.24.87.181) |
| 18:03:44 | <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 |
| 18:04:00 | → | liskin[m] joins (~liskinmat@2001:470:69fc:105::768) |
| 18:04:14 | → | unclechu joins (~unclechu@2001:470:69fc:105::354) |
| 18:07:46 | × | scrungus quits (~scrungus@70.24.87.181) (Quit: WeeChat 4.0.2) |
| 18:12:54 | → | scrungus joins (~scrungus@70.24.87.181) |
| 18:17:46 | × | geekosaur quits (~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b))) |
| 18:17:46 | → | allbery_b joins (~geekosaur@xmonad/geekosaur) |
| 18:17:49 | allbery_b | is now known as geekosaur |
| 18:19:17 | × | xmonadtrack quits (~xmonadtra@user/geekosaur/bot/xmonadtrack) (Ping timeout: 246 seconds) |
| 18:36:39 | × | scrungus quits (~scrungus@70.24.87.181) (Quit: WeeChat 4.0.2) |
| 18:41:28 | → | xmonadtrack joins (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 18:41:28 | × | xmonadtrack quits (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 18:41:28 | → | xmonadtrack joins (~xmonadtra@user/geekosaur/bot/xmonadtrack) |
| 21:19:40 | → | ft joins (~ft@p3e9bc856.dip0.t-ipconnect.de) |
| 22:03:32 | → | sagax joins (~sagax_nb@user/sagax) |
| 22:22:56 | × | mncheck quits (~mncheck@193.224.205.254) (Ping timeout: 245 seconds) |
| 23:24:36 | × | ft quits (~ft@p3e9bc856.dip0.t-ipconnect.de) (Ping timeout: 245 seconds) |
| 23:31:23 | → | ft joins (~ft@p3e9bcb94.dip0.t-ipconnect.de) |
All times are in UTC on 2023-07-19.