2022/05/01

2022-05-01 00:00:09 +0200noex(~null@user/noex)
2022-05-01 00:05:27 +0200noex(~null@user/noex) (Ping timeout: 276 seconds)
2022-05-01 00:07:26 +0200noex(~null@user/noex)
2022-05-01 00:17:33 +0200noex(~null@user/noex) (Ping timeout: 246 seconds)
2022-05-01 00:20:44 +0200noex(~null@user/noex)
2022-05-01 00:31:08 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d) (Ping timeout: 250 seconds)
2022-05-01 01:10:02 +0200Guest54(~Guest54@75-27-143-134.lightspeed.austtx.sbcglobal.net)
2022-05-01 01:12:08 +0200Guest54(~Guest54@75-27-143-134.lightspeed.austtx.sbcglobal.net) (Client Quit)
2022-05-01 02:42:59 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-05-01 02:48:13 +0200 <jakeStateless-Fa> @geekosaur that error just reoccurred, I haven't changed it to the hook version, and I'm away from my desktop now, but .xmonad/xmonad-errors doesn't have anything relevant and .xsession-errors is nonexistant on my system
2022-05-01 02:48:13 +0200 <lambdabot> Unknown command, try @list
2022-05-01 02:48:43 +0200 <jakeStateless-Fa> I am still not sure why it's erroring like that
2022-05-01 02:50:16 +0200 <jakeStateless-Fa> the hypothesis of it being layout related still remains, as I was able to open up apps and gridselect when I was there
2022-05-01 02:56:47 +0200 <abastro[m]> Perhaps you could try logging to separate file
2022-05-01 02:56:55 +0200 <abastro[m]> So that xmonad stuffs would be reported separately
2022-05-01 03:00:08 +0200abastro(~abab9579@220.75.216.63)
2022-05-01 03:02:13 +0200rekahsoft(~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com)
2022-05-01 03:05:29 +0200rekahsoft(~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) (Remote host closed the connection)
2022-05-01 03:05:54 +0200rekahsoft(~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com)
2022-05-01 03:11:09 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a)
2022-05-01 03:12:36 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a) (Read error: Connection reset by peer)
2022-05-01 03:12:52 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a)
2022-05-01 03:33:50 +0200stackdroid18(14094@user/stackdroid) (Quit: hasta la vista... tchau!)
2022-05-01 03:56:07 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a) (Quit: Konversation terminated!)
2022-05-01 04:03:49 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 256 seconds)
2022-05-01 04:22:44 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-05-01 04:30:42 +0200rekahsoft(~rekahsoft@cpe001b21a2fd89-cm64777ddc63a0.cpe.net.cable.rogers.com) (Ping timeout: 272 seconds)
2022-05-01 04:31:57 +0200td_(~td@muedsl-82-207-238-189.citykom.de) (Ping timeout: 276 seconds)
2022-05-01 04:32:25 +0200abastro(~abab9579@220.75.216.63) (Remote host closed the connection)
2022-05-01 04:33:29 +0200td_(~td@94.134.91.80)
2022-05-01 05:00:19 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Remote host closed the connection)
2022-05-01 05:02:00 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a)
2022-05-01 05:02:15 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-05-01 05:19:35 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a) (Quit: Konversation terminated!)
2022-05-01 05:27:02 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d)
2022-05-01 05:37:36 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 276 seconds)
2022-05-01 06:17:42 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 246 seconds)
2022-05-01 06:33:31 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net)
2022-05-01 07:07:22 +0200Ether17(~Ether17@45.248.151.250)
2022-05-01 07:18:03 +0200Ether17(~Ether17@45.248.151.250) (Quit: Client closed)
2022-05-01 07:54:09 +0200Ether17(~Ether17@45.248.151.250)
2022-05-01 07:54:32 +0200Ether17(~Ether17@45.248.151.250) (Client Quit)
2022-05-01 09:20:34 +0200gauge(~gauge@user/gauge)
2022-05-01 09:52:24 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d) (Ping timeout: 248 seconds)
2022-05-01 11:00:11 +0200jmac123[m](~jmac123ma@2001:470:69fc:105::1:eaf0) (Quit: You have been kicked for being idle)
2022-05-01 11:00:12 +0200robinhood0018[m](~robinhood@2001:470:69fc:105::1:4dca) (Quit: You have been kicked for being idle)
2022-05-01 11:00:15 +0200ctx[m](~ctxkungfu@2001:470:69fc:105::1:95dd) (Quit: You have been kicked for being idle)
2022-05-01 11:44:32 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 272 seconds)
2022-05-01 11:48:32 +0200Xioulious(~yourname@193.32.249.137) (Quit: leaving)
2022-05-01 11:54:07 +0200abastro(~abab9579@192.249.26.173)
2022-05-01 13:18:10 +0200abastro(~abab9579@192.249.26.173) (Remote host closed the connection)
2022-05-01 13:35:01 +0200td_(~td@94.134.91.80) (Ping timeout: 256 seconds)
2022-05-01 13:36:31 +0200td_(~td@94.134.91.69)
2022-05-01 13:46:48 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-05-01 15:12:24 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 248 seconds)
2022-05-01 15:33:16 +0200Xioulious(~yourname@193.32.249.137)
2022-05-01 15:36:14 +0200 <Xioulious> i've got a piece of code that makes it so with multiplescreens, when i move my mouse to a different screen that has an empty workspace, that screen/workspace gets focussed, this works as it should.. but then when i try to do the float and move with my mouse (the default modkey+buton1) and move the window to an other screen it often freaks out (starts jumping around) and sometimes goes invisible.. not
2022-05-01 15:36:20 +0200 <Xioulious> sure whats wrong with my code, could anyone take a look at it?
2022-05-01 15:36:36 +0200 <Xioulious> move a window*
2022-05-01 15:38:15 +0200 <geekosaur> you should probably pastebin the code so someone can look at it, rather than asking to ask
2022-05-01 15:38:19 +0200 <geekosaur> @where paste
2022-05-01 15:38:19 +0200 <lambdabot> Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com
2022-05-01 15:38:48 +0200 <geekosaur> I don't know how long I'll be around today, I'm waiting on my sister as usual for a Sunday
2022-05-01 15:41:50 +0200 <Xioulious> should i put my full xmonad.hs there or just the piece of code thats bugging out? guessing the xmonad.hs might be easier?
2022-05-01 15:41:54 +0200 <geekosaur> aaaand there she is
2022-05-01 15:42:04 +0200 <geekosaur> yes, seeing how it integrates in is often helpful
2022-05-01 15:42:17 +0200 <Xioulious> haha, enjoy your day with your sis!
2022-05-01 15:42:20 +0200 <Xioulious> ok, will do
2022-05-01 15:42:27 +0200 <geekosaur> \might want to use gist in that case. (many of us host our xmonad.hs-s on github or gitlab to make this easier)
2022-05-01 15:42:45 +0200 <geekosaur> well, I hae around an hour; she just texted me
2022-05-01 15:43:18 +0200 <geekosaur> *have
2022-05-01 15:43:27 +0200 <Xioulious> yeah i already got my xmonad.hs on my gitlab, though i do get some errors in my xsession-error file which could be helpfull
2022-05-01 15:46:42 +0200 <Xioulious> https://paste.tomsmeding.com/T6dIGYxa thats the stack.yaml and the error log, https://gitlab.com/Shadu/dotfiles/-/blob/main/.config/xmonad/xmonad.hs is the xmonad.hs
2022-05-01 15:48:26 +0200 <Xioulious> if i comment out the multiScreenFocusHook then it doesnt happen, but ofc then it wont focus on an empty workspace automatically
2022-05-01 15:49:16 +0200 <geekosaur> it never rains but it pours :) I wonder if this is the one we hit yesterday (BadValue on request 91/XLookupColor)
2022-05-01 15:50:23 +0200 <Xioulious> yeah, during normal use that error also pops up sometimes, but when i do that specific thing then it just floods it
2022-05-01 15:51:05 +0200 <geekosaur> and there's WindowNavigation, which might be the cause
2022-05-01 15:53:32 +0200 <Xioulious> hmm then i wonder about something, the person i got that script from didnt really encounter the problem, but i didnt take their layout setup.. let me check if they use windownavigation
2022-05-01 15:54:39 +0200 <Xioulious> nope, they aren't using it
2022-05-01 15:58:11 +0200 <geekosaur> that is likely to be the cause of the errors in the log, from our debugging over the past several hours of someone else's config
2022-05-01 15:58:51 +0200 <geekosaur> but I suspect your dragging problem is because you have both draggingVisualizer and multiScreenFocusHook and they're fighting each other
2022-05-01 15:58:59 +0200 <Xioulious> the freaking out still occurs even if i comment out the windownavigation import and the part in the layout
2022-05-01 16:00:30 +0200 <Xioulious> for some reason it seems to want to stretch the window downwards, atleast the size of the window changes when it does that
2022-05-01 16:02:27 +0200 <Xioulious> also seems to only do it when i drag a window to an empty workspace
2022-05-01 16:04:20 +0200 <Xioulious> got some better errors this time, but thats with a firefox crash: https://paste.tomsmeding.com/WOW4bhC2
2022-05-01 16:11:24 +0200 <geekosaur> the getWindowAttributes errors are sadly normal. BadAlloc looks bad, though
2022-05-01 16:11:47 +0200 <geekosaur> what happens if you disable DraggingVisualizer?
2022-05-01 16:12:51 +0200 <Xioulious> still the same behavior
2022-05-01 16:13:15 +0200 <geekosaur> okay, so it's not a conflict there
2022-05-01 16:20:18 +0200 <Xioulious> if i do the same but with a thunar window, it also freaks out, but i dont get the badalloc error, so am thinking the badalloc is an error on firefox side?
2022-05-01 16:20:47 +0200 <geekosaur> except it's xmonad reporting it (note the start of the line)
2022-05-01 16:21:02 +0200 <Xioulious> it also doesnt add any errors to the xsession-error file in the case of thunar
2022-05-01 16:21:34 +0200 <geekosaur> ConfigureWindow
2022-05-01 16:21:41 +0200 <Xioulious> true, just thought that if there are some x11 errors that arent caused by xmonad but by a program running that xmonad would be reporting it or something
2022-05-01 16:22:07 +0200 <geekosaur> no, xmonad wouldn't receive those errors
2022-05-01 16:22:27 +0200 <geekosaur> ConfigureWindow error would match with your remark about the window resizing
2022-05-01 16:26:23 +0200 <Xioulious> could that have something to do with having 2 different resolutions? (monitor 1 being 1920x1200, monitor 2 being 1920x1080)
2022-05-01 16:26:57 +0200thunderrd(~thunderrd@183.182.110.239) (Remote host closed the connection)
2022-05-01 16:27:55 +0200 <geekosaur> yes. xmonad stores relative sizes (see RationalRect) and will resize (in your case, downward) when you move a window to a different monitor
2022-05-01 16:28:02 +0200thunderrd(~thunderrd@183.182.110.239)
2022-05-01 16:28:37 +0200 <geekosaur> I think your hook needs to verify that it is not inside a window at the time
2022-05-01 16:29:57 +0200 <geekosaur> it's not enough to check that there are no windows "on the screen" because the window you're moving won't be registered as on that screen until its origin is there
2022-05-01 16:30:15 +0200 <geekosaur> that is, its (0,0)
2022-05-01 16:30:22 +0200 <geekosaur> upper left corner
2022-05-01 16:30:34 +0200 <geekosaur> and may not be actually moved until the drag stops
2022-05-01 16:32:03 +0200 <Xioulious> so the hook for the focus thing should only activate when the cursor itself isnt over a window instead of checking if the screen has any windows
2022-05-01 16:32:49 +0200 <geekosaur> right, because "screen has any windows" will be incorrect mid-drag
2022-05-01 16:34:35 +0200 <geekosaur> queryPointer should inform you both of the pointer location and what window it's currently in
2022-05-01 16:35:04 +0200 <Xioulious> and then the hook will try to focus the workspace but then when i drag some more i throw the focus back to the window and it will constantly jump between those 2 and things freak out, sounds logical yeah, now to figure out how to implement it
2022-05-01 16:37:58 +0200cfricke(~cfricke@user/cfricke)
2022-05-01 16:38:28 +0200 <geekosaur> https://hackage.haskell.org/package/X11-1.10.2/docs/Graphics-X11-Xlib-Misc.html#v:queryPointer https://tronche.com/gui/x/xlib/window-information/XQueryPointer.html
2022-05-01 16:38:53 +0200 <geekosaur> the Haskell wrapper is pretty raw, it maps directly to the Xlib call
2022-05-01 16:39:16 +0200 <geekosaur> so you can just check if the returned window ID (not root window ID) is 0
2022-05-01 16:40:26 +0200 <abastro[m]> Interesting how such direct translation is possible
2022-05-01 16:40:29 +0200 <Xioulious> okay, let me make a note of that, time to learn some haskell
2022-05-01 16:43:56 +0200 <Xioulious> also another bug that im having, though its with xmobar, is when I have my TV that is connected to my pc turned on but disabled through xrandr (or well, nvidia settings) and my 2 monitors go into standby, when i wake the monitors back up the xmobars are stretched across both screens
2022-05-01 16:44:52 +0200 <geekosaur> that would imply that xrandr information is wrong. I think we've seen that a few times with nvidia
2022-05-01 16:45:33 +0200 <geekosaur> sometimes affects xmonad as well, the xrandr information is inconsistent and different programs use different parts of it
2022-05-01 16:46:12 +0200 <abastro[m]> X & multiscreen?
2022-05-01 16:46:56 +0200 <Xioulious> so when that occurs i should check what xrandr is saying? i usually just do a recompile and restart of xmonad and that fixes it, but rather have it not occur ofc
2022-05-01 16:46:58 +0200 <geekosaur> multiscreen is a horrid hack, it's amazing that it works we well as it does
2022-05-01 16:47:53 +0200 <abastro[m]> I am glad I only have this laptop with single screen
2022-05-01 16:47:56 +0200 <geekosaur> X supports multiscreen natively but assumes every screen has its own framebuffer so windows can't be moved between them or etc., because that's how things worked in the 1980s
2022-05-01 16:48:37 +0200 <Xioulious> mhm, seems with nvidia it just makes 1 big screen and divides it up in 2 spaces
2022-05-01 16:49:38 +0200 <abastro[m]> Linux distros do not usually depend on X, right
2022-05-01 16:49:43 +0200 <geekosaur> that's how the multiscreen hack works,m yes. not just nvidia
2022-05-01 16:50:18 +0200 <geekosaur> it means different monitor resolutions don't work right, and various other shortcomings
2022-05-01 16:50:35 +0200 <abastro[m]> Nvidia?
2022-05-01 16:50:58 +0200 <geekosaur> alll the big linux distros still depend on X. we're expecting it to still be supported through 2030 because of contractual obligations on Red Hat's commercial offerings
2022-05-01 16:51:06 +0200 <Xioulious> that also causes the issues of different refreshrates, sadly wayland isnt ready yet for daily use for me, but xmonad feels way more comfy than i3 so far
2022-05-01 16:52:51 +0200 <geekosaur> abastro[m], as I said, not just nvidia
2022-05-01 16:53:00 +0200 <abastro[m]> Is xmonad that good?
2022-05-01 16:53:04 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a)
2022-05-01 16:53:19 +0200 <geekosaur> that;s something of a personal question, I think :)
2022-05-01 16:53:45 +0200 <abastro[m]> geekosaur: on "not just nvidia": Does that mean even Windows does not get it right?
2022-05-01 16:54:26 +0200 <geekosaur> Windows (and Wayland) use a different screen model. in particular Windows gets it more correct than any Linux environment including current Wayland
2022-05-01 16:54:28 +0200 <Xioulious> he meant that amd, intel and nvidia make 1 big screen for all your monitors and then divide spaces in that screen that each monitor/display gets assigned in X
2022-05-01 16:54:45 +0200 <geekosaur> ^ which is X's fault
2022-05-01 16:55:06 +0200 <geekosaur> X simply can't do this right becuase its core was designed in the 1980s when things worked differently
2022-05-01 16:55:55 +0200 <Xioulious> about xmonad, i like the way you configure it and what you can make it do, you can get pretty far with just grabbig stuff from other people's configs to get it to do what you want it to do, but when you want to adjust it a bit on your own it becomes hard unless you already know haskell
2022-05-01 16:56:33 +0200 <Solid> sounds like a perfect excuse to learn haskell :)
2022-05-01 16:56:52 +0200 <abastro[m]> Wait, so you mean the drivers
2022-05-01 16:56:57 +0200 <Xioulious> yeah, i need to start learning it now to make my hook work for my situation
2022-05-01 16:57:41 +0200 <abastro[m]> geekosaur: Yea, sad that this kind of problem could only be fixed with money being put in
2022-05-01 16:58:23 +0200 <Xioulious> even with money that would be a lot of money needed for anyone to dive that deep into the X code to adjust it, especially now that wayland is becoming bigger
2022-05-01 16:59:11 +0200 <abastro[m]> Well I meant how Windows handles it better
2022-05-01 17:00:40 +0200 <Xioulious> i dont think wayland will be that far behind windows in that aspect with time, as more distro's swap over to it more attention and improvements will go to it i hope
2022-05-01 17:05:03 +0200 <abastro[m]> I see
2022-05-01 17:05:28 +0200 <abastro[m]> In that case, xmonad would also eventually transfer to wayland I guess
2022-05-01 17:06:56 +0200 <Xioulious> when i read about that a bit ago somewhere it was mentioned that moving xmonad to wayland would require a big rewrite of stuff, also wouldnt be called xmonad (as the X in xmonad stands for X11) there was already some work done on a wayland version but it hasnt been updated in a bit if i remember right
2022-05-01 17:08:19 +0200 <geekosaur> X11 needs more than just money put in, it needs a complete redesign to make it more like Wayland
2022-05-01 17:08:29 +0200 <geekosaur> wouldn't be so much X12 as Y1
2022-05-01 17:08:57 +0200 <geekosaur> but wayland is here now. it just needs to mature a bit (well, a lot)
2022-05-01 17:09:08 +0200 <Xioulious> X11 is also very insecure, while wayland is way better at that part
2022-05-01 17:09:28 +0200 <geekosaur> yes, its security model is as 1980s as the rest of it
2022-05-01 17:10:24 +0200 <Solid> i feel like most of the "security" features of wayland (like how something akin to xdotool could never work as well) are more of a theater show and actually very detrimental to user experience
2022-05-01 17:11:13 +0200 <Xioulious> currently, agreed, like screensharing, but programs are starting to implement things so that it works, thats part of the lots of maturing it still has to do
2022-05-01 17:11:50 +0200 <Solid> programs will also have to implement it n times, where n is the number of compositors they want to support
2022-05-01 17:11:57 +0200 <Solid> sounds like a lot of fun
2022-05-01 17:12:12 +0200 <abastro[m]> Xd
2022-05-01 17:12:44 +0200 <geekosaur> that also is arguably part of the maturing, compositors need to agree on some standards
2022-05-01 17:13:57 +0200 <geekosaur> sadly, given current linux politics that probably means everyone being railroaded into accepting weston as *the* standard
2022-05-01 17:14:11 +0200 <Solid> GNOME and KDE agreeing on a standard? I'll bevlieve it when I see it
2022-05-01 17:14:37 +0200 <geekosaur> they did, once
2022-05-01 17:14:44 +0200 <geekosaur> that's where ewmh came from
2022-05-01 17:15:06 +0200 <Xioulious> hope supporting nvidia with wayland will also become easier to do for them
2022-05-01 17:16:27 +0200 <liskin> Nvidia & Wayland should kinda just work with the latest drivers, I thought? Perhaps there are bugs but the missing apis are already there
2022-05-01 17:17:19 +0200 <Xioulious> you can run it, but yeah quite some bugs, mostly for me parts of certain windows flickering and believe i read somewhere that that was due to vsync related issues though could be remembering wrong
2022-05-01 17:17:44 +0200 <Xioulious> and figuring out what is exactly causing that problem becomes hard when you can only see one side of the code
2022-05-01 17:17:57 +0200 <liskin> Oh I see. Never tried it myself.
2022-05-01 17:18:40 +0200 <Xioulious> i also had worse performance in games, but thats more so an xwayland problem i think
2022-05-01 17:19:45 +0200 <liskin> Solid, mc47: have you guys already got a hotel reservation for ZuriHac, btw?
2022-05-01 17:21:04 +0200 <abastro[m]> Did not know display standard would be as hard as entire OS
2022-05-01 17:23:20 +0200 <abastro[m]> How can I "learn" wayland and its philosophy alike how I learn linux kernel
2022-05-01 17:23:31 +0200 <Solid> liskin: yeah, all done already
2022-05-01 17:28:02 +0200c209e6dc-4d76-47(~aditya@2601:249:4300:1296:195:dac6:592c:a55a) (Quit: Konversation terminated!)
2022-05-01 17:32:54 +0200 <liskin> Hm, okay, perhaps I should as well then. How far from the venue are you?
2022-05-01 17:32:55 +0200 <abastro[m]> ""A display server using the Wayland protocol is called a Wayland compositor, because it additionally performs the task of a compositing window manager.""
2022-05-01 17:33:49 +0200 <Solid> liskin: walking distance; like 800m or so if I remember correctly
2022-05-01 17:34:25 +0200 <geekosaur> right, while X11 is built around the window manager and a compositor is an add-on, wayland is built around the compositor and makes window management the not-quite-add-on
2022-05-01 17:34:56 +0200 <geekosaur> this actually makes sense functionally; compositing is yet another hack in the X11 world, but it *really* ought to be part of the display server
2022-05-01 17:36:39 +0200 <abastro[m]> geekosaur: Interesting, btw doesn't this mean Wayland WM should implement compositor?
2022-05-01 17:37:01 +0200 <abastro[m]> geekosaur: (also is it okay to have multiple convos in an irc channel)
2022-05-01 17:37:05 +0200 <geekosaur> no. consider that window management is a plugin in gnome
2022-05-01 17:37:14 +0200 <geekosaur> it's okay, it just gets confusing at times
2022-05-01 17:37:38 +0200 <geekosaur> window management is not about operation, it's about policy
2022-05-01 17:38:10 +0200 <geekosaur> so having it as a plugin is reasonable (and in fact it is in some sense a plugin in the X11 world as well)
2022-05-01 17:38:31 +0200 <geekosaur> you can actually operate an X server without a window manager, it just sucks a whole lot
2022-05-01 17:39:08 +0200 <abastro[m]> Ohh
2022-05-01 17:39:26 +0200 <abastro[m]> So xmonad is also about the policy, I guess
2022-05-01 17:39:41 +0200 <abastro[m]> (Tho some might create DM out of xmonad)
2022-05-01 17:39:48 +0200 <geekosaur> all you need is an open terminal and you run everything from that and manually provide -geometry parameters to place the windows
2022-05-01 17:41:15 +0200 <abastro[m]> XD
2022-05-01 17:41:45 +0200 <abastro[m]> In that case, why would it be quite hard to port xmonad on wayland?
2022-05-01 17:41:56 +0200 <abastro[m]> If it is going to be a plugin
2022-05-01 17:42:00 +0200 <geekosaur> I've done that while debugging xmonad crashes, for instance
2022-05-01 17:42:27 +0200 <geekosaur> because xmonad's internals are really tightly tied to Xlib APIs
2022-05-01 17:42:36 +0200 <geekosaur> we couldn't even move it to xcb sanely
2022-05-01 17:43:12 +0200 <abastro[m]> Xlib APIs?
2022-05-01 17:43:37 +0200 <abastro[m]> Oh right, wm plugins should at least be able to move stuffs around
2022-05-01 17:43:51 +0200 <abastro[m]> Which means interfacing with the protocol
2022-05-01 17:44:36 +0200 <liskin> If we had a well-maintained compositor with an API for window-manager plugins, porting the core parts of xmonad wouldn't be hard.
2022-05-01 17:44:47 +0200 <liskin> xmonad-contrib is another story though
2022-05-01 17:44:55 +0200 <geekosaur> right
2022-05-01 17:45:15 +0200 <abastro[m]> Xmonad-contrib, that sounds like manpower problem
2022-05-01 17:45:40 +0200 <abastro[m]> Oh wait. So wayland does not yet gave good APIs for WM?
2022-05-01 17:45:58 +0200 <abastro[m]> Wayland compositors does not yet provide APIs*
2022-05-01 17:46:08 +0200 <liskin> The existing compositors happen to be WMs as well
2022-05-01 17:46:23 +0200 <abastro[m]> Oh no
2022-05-01 17:46:28 +0200 <abastro[m]> *Whi*
2022-05-01 17:46:47 +0200 <liskin> So GNOME has its own, KDE its own, sway its own.
2022-05-01 17:46:53 +0200 <abastro[m]> I guess ppl love such coupling..
2022-05-01 17:47:13 +0200 <liskin> Although that was the case with X11 as well, but you could mix and match. Now you can't.
2022-05-01 17:47:59 +0200 <liskin> Coupling saves you development time. Less communication, less protocol design committees.
2022-05-01 17:49:06 +0200 <abastro[m]> Yea..
2022-05-01 17:49:27 +0200 <abastro[m]> So that might be why xmonad could have less place
2022-05-01 17:49:42 +0200 <abastro[m]> Was waymonad project trying to make a whole compositor, then?
2022-05-01 17:49:53 +0200mvk(~mvk@2607:fea8:5ce3:8500::aa1d)
2022-05-01 17:50:56 +0200 <abastro[m]> (..wait I guess I myself also likes coupling, once I tried to put a status bar into xmonad executable)
2022-05-01 17:54:57 +0200 <abastro[m]> geekosaur: Was waymonad an entire wayland compositor?
2022-05-01 17:56:07 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net)
2022-05-01 17:57:59 +0200 <abastro[m]> Hmm wayland protocol is.. asynchronous object-oriented protocol
2022-05-01 17:58:04 +0200 <abastro[m]> Meh
2022-05-01 18:00:19 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2022-05-01 18:02:13 +0200Anexploringbot[m(~wybpipmat@2001:470:69fc:105::1:f452)
2022-05-01 18:02:14 +0200Anexploringbot[m(~wybpipmat@2001:470:69fc:105::1:f452) ()
2022-05-01 18:14:02 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 272 seconds)
2022-05-01 18:44:53 +0200 <liskin> abastro[m]: Yes, waymonad is a whole compositor/window-manager in one process.
2022-05-01 18:45:05 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-05-01 18:45:26 +0200 <liskin> The compositor part is largely implemented using the wlroots library, so it's not an entirely separate implementation, though.
2022-05-01 18:46:19 +0200 <liskin> But my knowledge ends about here, unfortunately.
2022-05-01 19:44:05 +0200 <yuu[m]> <abastro[m]> "Meh..." <- why?
2022-05-01 20:02:01 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-05-01 20:36:45 +0200 <Xioulious> according to https://github.com/xmonad/xmonad/issues/104 i shouldn't need a function to focus an empty workspace when i move my cursor there, or is this somehow reverted? as i added a function to get that functionality
2022-05-01 20:51:54 +0200benin(~benin@183.82.204.110)
2022-05-01 21:16:19 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-05-01 21:25:56 +0200steve__(~steve@ool-182c2b80.dyn.optonline.net) (Ping timeout: 272 seconds)
2022-05-01 21:29:45 +0200benin(~benin@183.82.204.110) (Quit: The Lounge - https://thelounge.chat)
2022-05-01 22:14:35 +0200dschrempf(~dominik@070-207.dynamic.dsl.fonira.net) (Quit: WeeChat 3.4.1)
2022-05-01 22:48:25 +0200stackdroid18(14094@user/stackdroid)
2022-05-01 23:56:15 +0200 <geekosaur> Xioulious, do you know that you needed to add a function? Often things are cargo-culted and copied around for years when they're not needed any more.