| 2022-10-28 00:03:38 +0200 | <geekosaur> | not so far as I'm aware |
| 2022-10-28 00:11:03 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving) |
| 2022-10-28 00:11:46 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-10-28 00:24:27 +0200 | mncheck | (~mncheck@193.224.205.254) (Ping timeout: 272 seconds) |
| 2022-10-28 00:57:44 +0200 | noex | (~null@user/noex) (Quit: :q!) |
| 2022-10-28 01:22:13 +0200 | jabuxas | (~klein@user/jabuxas) (Quit: WeeChat 3.5) |
| 2022-10-28 01:28:50 +0200 | darkstardevx | (~darkstard@50.126.124.156) (Remote host closed the connection) |
| 2022-10-28 01:31:17 +0200 | darkstardevx | (~darkstard@50.126.124.156) |
| 2022-10-28 01:35:50 +0200 | darkstardevx | (~darkstard@50.126.124.156) (Max SendQ exceeded) |
| 2022-10-28 01:50:39 +0200 | darkstardevx | (~darkstard@50.126.124.156) |
| 2022-10-28 01:52:29 +0200 | darkstardevx | (~darkstard@50.126.124.156) (Max SendQ exceeded) |
| 2022-10-28 01:53:20 +0200 | darkstardevx | (~darkstard@50.126.124.156) |
| 2022-10-28 01:58:40 +0200 | chomwitt | (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) (Ping timeout: 255 seconds) |
| 2022-10-28 02:07:03 +0200 | ft | (~ft@p3e9bc845.dip0.t-ipconnect.de) (Ping timeout: 272 seconds) |
| 2022-10-28 02:08:09 +0200 | ft | (~ft@p508dbd59.dip0.t-ipconnect.de) |
| 2022-10-28 03:26:13 +0200 | Natch | (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) (Ping timeout: 272 seconds) |
| 2022-10-28 03:29:23 +0200 | Natch | (~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) |
| 2022-10-28 04:02:36 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 250 seconds) |
| 2022-10-28 04:08:51 +0200 | td_ | (~td@83.135.9.51) (Ping timeout: 260 seconds) |
| 2022-10-28 04:10:20 +0200 | td_ | (~td@83.135.9.42) |
| 2022-10-28 04:23:15 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
| 2022-10-28 04:43:13 +0200 | terrorjack | (~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat) |
| 2022-10-28 04:45:46 +0200 | terrorjack | (~terrorjac@2a01:4f8:1c1e:509a::1) |
| 2022-10-28 05:06:08 +0200 | noex | (~null@user/noex) |
| 2022-10-28 05:53:57 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 240 seconds) |
| 2022-10-28 07:43:16 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving) |
| 2022-10-28 07:44:22 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-10-28 07:56:55 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving) |
| 2022-10-28 07:58:30 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-10-28 08:01:19 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) (Client Quit) |
| 2022-10-28 08:02:22 +0200 | Maeda | (~Maeda@91-161-10-149.subs.proxad.net) |
| 2022-10-28 09:15:34 +0200 | m5zs7k | (aquares@web10.mydevil.net) (Ping timeout: 244 seconds) |
| 2022-10-28 09:16:41 +0200 | m5zs7k | (aquares@web10.mydevil.net) |
| 2022-10-28 09:18:43 +0200 | mncheck | (~mncheck@193.224.205.254) |
| 2022-10-28 09:25:59 +0200 | ft | (~ft@p508dbd59.dip0.t-ipconnect.de) (Quit: leaving) |
| 2022-10-28 09:29:00 +0200 | <xmonadtrack> | New xmonad-contrib branch created: pull/770 (1 commit) https://github.com/xmonad/xmonad-contrib/pull/770 |
| 2022-10-28 09:29:00 +0200 | <xmonadtrack> | xmonad-contrib Tony Zorman https://github.com/xmonad/xmonad-contrib/pull/770 * v0.17.1-51-gf9928ec5: New module: XMonad.Hooks.OnPropertyChange (77 minutes ago, 4 files, 134+ 1-) https://github.com/xmonad/xmonad-contrib/commit/f9928ec5f4e1 |
| 2022-10-28 10:01:45 +0200 | sogens | (sogens@gateway/vpn/protonvpn/sogens) |
| 2022-10-28 10:12:28 +0200 | cfricke | (~cfricke@user/cfricke) |
| 2022-10-28 11:00:29 +0200 | Alok[m] | (~alok8bbma@2001:470:69fc:105::2:620f) (Quit: You have been kicked for being idle) |
| 2022-10-28 11:00:41 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle) |
| 2022-10-28 12:19:48 +0200 | td_ | (~td@83.135.9.42) (Ping timeout: 252 seconds) |
| 2022-10-28 12:29:26 +0200 | td_ | (~td@83.135.9.42) |
| 2022-10-28 13:13:26 +0200 | liskin | tries to simplify the above a bit further |
| 2022-10-28 13:13:38 +0200 | liskin[m] | (~liskinmat@2001:470:69fc:105::768) |
| 2022-10-28 14:15:03 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
| 2022-10-28 14:15:09 +0200 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) (Remote host closed the connection) |
| 2022-10-28 14:17:36 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
| 2022-10-28 14:19:53 +0200 | chomwitt | (~chomwitt@2a02:587:dc10:8200:1ac0:4dff:fedb:a3f1) |
| 2022-10-28 14:20:38 +0200 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) |
| 2022-10-28 14:20:38 +0200 | xmonadtrack | (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host) |
| 2022-10-28 14:20:38 +0200 | xmonadtrack | (~xmonadtra@xmonad/geekosaur) |
| 2022-10-28 14:56:19 +0200 | purity-gearD[m] | (~pipe-gear@2001:470:69fc:105::2:ac18) |
| 2022-10-28 15:02:51 +0200 | <Solid> | Should've thought of that myself; thanks :) |
| 2022-10-28 15:14:54 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-10-28 15:32:57 +0200 | ft | (~ft@p508dbd59.dip0.t-ipconnect.de) |
| 2022-10-28 15:39:23 +0200 | cfricke | (~cfricke@user/cfricke) (Quit: WeeChat 3.7.1) |
| 2022-10-28 16:02:17 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 240 seconds) |
| 2022-10-28 16:07:03 +0200 | mncheck | (~mncheck@193.224.205.254) (Quit: Leaving) |
| 2022-10-28 16:07:09 +0200 | mncheckm | (~mncheck@193.224.205.254) |
| 2022-10-28 16:27:04 +0200 | sogens | (sogens@gateway/vpn/protonvpn/sogens) (Ping timeout: 250 seconds) |
| 2022-10-28 16:30:00 +0200 | sogens | (~sogens@pa49-182-84-76.pa.qld.optusnet.com.au) |
| 2022-10-28 16:35:59 +0200 | sogens | (~sogens@pa49-182-84-76.pa.qld.optusnet.com.au) (Ping timeout: 272 seconds) |
| 2022-10-28 16:37:19 +0200 | sogens | (sogens@gateway/vpn/protonvpn/sogens) |
| 2022-10-28 16:48:34 +0200 | <reo42[m]> | Is there a way of changing border colors dynamically without reloading xmonad? |
| 2022-10-28 16:53:44 +0200 | <geekosaur> | no |
| 2022-10-28 16:56:10 +0200 | <geekosaur> | I guess conceivably the constant colors could be replaced by `unsafePerformIO (readIOVar myColorVar)` with an appropriate `myColorVar` for each one, but it's as unsafe as the name suggests |
| 2022-10-28 16:56:22 +0200 | <geekosaur> | er, `readIORef` |
| 2022-10-28 16:57:23 +0200 | <geekosaur> | you'd have to `refresh` after changing the colors in the `IORef`s |
| 2022-10-28 17:03:24 +0200 | <geekosaur> | (also don't forget to `{-# NOINLINE myColorVar #-}` after declaring it (at top level with `myColorVar = unsafePerformIO (newIORef initialValue)` for some `initialValue`) or you may find changes don't happen) |
| 2022-10-28 17:11:05 +0200 | fewu[m] | (~fewumatri@2001:470:69fc:105::2:ad68) |
| 2022-10-28 17:33:21 +0200 | <[Leary]> | Are there any layout,logHook pairs in contrib such that running the layout causes changes/effects that the logHook needs to see? Put another way, would it be bad for the logHook to run before the layout? |
| 2022-10-28 17:35:05 +0200 | <reo42[m]> | <geekosaur> "I guess conceivably the constant..." <- Ok, thanks (btw you can use double backticks for inline code |
| 2022-10-28 17:35:05 +0200 | <reo42[m]> | * inline code) |
| 2022-10-28 17:41:50 +0200 | <geekosaur[m]> | Not in an IRC client |
| 2022-10-28 17:42:33 +0200 | <geekosaur[m]> | (temporarily on matrix now) |
| 2022-10-28 18:00:05 +0200 | arslonga[m] | (~uuuuuuuum@2001:470:69fc:105::1589) (Quit: You have been kicked for being idle) |
| 2022-10-28 18:00:05 +0200 | NONstope[m] | (~nonstopem@2001:470:69fc:105::2:8d1c) (Quit: You have been kicked for being idle) |
| 2022-10-28 18:09:20 +0200 | jao | (~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) |
| 2022-10-28 18:25:20 +0200 | <reo42[m]> | <geekosaur[m]> "Not in an IRC client..." <- Oh, yeah, it's all about client. This works on element. |
| 2022-10-28 18:25:45 +0200 | <reo42[m]> | s/This/That/ |
| 2022-10-28 18:28:57 +0200 | <geekosaur> | well, some things can be done irc side and they'll show up in element |
| 2022-10-28 18:31:42 +0200 | <geekosaur> | [Leary], the only special case I can think of off the top of my head is some consumer of the `logHook` might care that `SimplestFloat` floats every window it's asked to manage |
| 2022-10-28 18:33:14 +0200 | <geekosaur> | granting I haven't looked at how to does so and it might actually trigger a loop (which would eventually stop when it found nothing left to float and stopped calling `windows`) |
| 2022-10-28 18:34:36 +0200 | <geekosaur> | oh, huh, `SimpleFloat` doesn't actually float them by xmonad's definition thereof |
| 2022-10-28 18:35:00 +0200 | <geekosaur> | I'd wondered about writing such a layout… guess it exists already |
| 2022-10-28 18:37:07 +0200 | <geekosaur> | in any case, rearranging / changing that sequence has caused surprises in the past (at one point an "optimization" broke Tabbed, for example) so you would want to test such a change fairly thoroughly |
| 2022-10-28 18:38:32 +0200 | <[Leary]> | I've actually been running on it for a while, but my config only touches so much of contrib; there's way too much esoteric crap in there I could be breaking. |
| 2022-10-28 18:41:31 +0200 | <[Leary]> | Maybe it's fine to break it. <.< |
| 2022-10-28 18:41:53 +0200 | <geekosaur> | technically the `layoutHook` shouldn't be capable of breaking `logHook` (without breaking everything else in the process, and in particular causing an infinite loop in `windows`) |
| 2022-10-28 18:46:08 +0200 | <[Leary]> | This is part of a WIP PR wherein changes made by the logHook would be handled alongside the user changes that prompted the refresh, in such a manner as to preclude that loop without leaving unhandled changes in the windowset. |
| 2022-10-28 18:46:28 +0200 | <[Leary]> | But for that to work, it needs to run before `windows` itself, and hence before the layouts. |
| 2022-10-28 18:47:01 +0200 | <geekosaur> | the `logHook` should not make changes; it's there to report changes |
| 2022-10-28 18:47:18 +0200 | <geekosaur> | running it before `windows` would mean it lagged current state, no? |
| 2022-10-28 18:47:33 +0200 | <geekosaur> | in particular, switching current workspace goes through `windows` |
| 2022-10-28 18:49:05 +0200 | <[Leary]> | No, it would be like `old <- gets windowset; userAction; logHook; new <- gets windowset; modifyWindowSet (const old); windows (const new)`. |
| 2022-10-28 18:50:01 +0200 | <[Leary]> | And right, it certainly isn't designed to make changes, but users can put such code there, and we ought to handle it without breaking. It's also better, I think, if you /can/ put changes there, as a "refreshHook" would be useful. |
| 2022-10-28 18:51:06 +0200 | <geekosaur> | mm, not quite seeing it. but I'm about to catch a bus so I'm a bit distracted… |
| 2022-10-28 18:52:42 +0200 | <[Leary]> | Have a look at `X.O.windowBracket` when you get the chance; this logic is already implemented there and used in `sendMessage`. |
| 2022-10-28 19:32:38 +0200 | sadmax2 | (~user@cpe-76-186-137-164.tx.res.rr.com) |
| 2022-10-28 19:34:50 +0200 | sadmax2 | (~user@cpe-76-186-137-164.tx.res.rr.com) (Remote host closed the connection) |
| 2022-10-28 19:41:29 +0200 | sadmax | (~user@cpe-76-186-137-164.tx.res.rr.com) |
| 2022-10-28 19:55:45 +0200 | <dminuoso> | So slack in the newest version decides to seemingly draw a white square in the middle of a window when a huddle is opened. |
| 2022-10-28 19:56:10 +0200 | <dminuoso> | Given that xprop returns only with the window manager, Im wondering: is there a mechanism for programs to draw directly on canvas without a window? |
| 2022-10-28 19:56:59 +0200 | <dminuoso> | That white rectangle something is also not draggable, but seems to be a) behind windows that are being dragged, a) behind windows that are not pushed in, but c) in front of everything else |
| 2022-10-28 19:58:06 +0200 | <dminuoso> | (or rather, xprop will return information for whatever is behind that square |
| 2022-10-28 19:58:06 +0200 | berberman | (~berberman@user/berberman) (Ping timeout: 250 seconds) |
| 2022-10-28 19:59:46 +0200 | <dminuoso> | https://i.imgur.com/sbuUpuS.png is what it looks like |
| 2022-10-28 20:18:17 +0200 | sadmax | (~user@cpe-76-186-137-164.tx.res.rr.com) (Ping timeout: 272 seconds) |
| 2022-10-28 21:12:03 +0200 | <geekosaur> | you can't just scribble over other windows like that in X11 |
| 2022-10-28 21:14:14 +0200 | <geekosaur> | X clips at window borders, so the closest you'd get is drawing to the root window but that would appear below all other windows |
| 2022-10-28 21:15:27 +0200 | <geekosaur> | what you describe for its z-placement sounds like it's a floating window, possibly unmanaged (but then, why is xprop not working?) |
| 2022-10-28 21:15:34 +0200 | <geekosaur> | does xwininfo work? |
| 2022-10-28 21:17:52 +0200 | <geekosaur> | [Leary], interesting. I see you added those in 2018. I'll defer to liskin on this but if it's working for you then it's probably okay |
| 2022-10-28 21:23:18 +0200 | thyriaen | (~thyriaen@2a01:aea0:dd4:470d:6245:cbff:fe9f:48b1) |
| 2022-10-28 21:24:35 +0200 | <geekosaur> | sorry for delays, I was at the store |
| 2022-10-28 21:30:56 +0200 | <[Leary]> | No worries, thanks for looking into it. |
| 2022-10-28 21:36:40 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::f30b) |
| 2022-10-28 21:43:28 +0200 | sogens | (sogens@gateway/vpn/protonvpn/sogens) (Quit: WeeChat 3.6) |
| 2022-10-28 22:30:10 +0200 | wusticality | (~user@76.131.115.3) |
| 2022-10-28 23:06:07 +0200 | mncheckm | (~mncheck@193.224.205.254) (Ping timeout: 272 seconds) |
| 2022-10-28 23:07:03 +0200 | Guest7732 | (~Guest77@109.98.214.166) |
| 2022-10-28 23:08:29 +0200 | <Guest7732> | Hi, I am new to XMonad and I was wondering if I could have rounded cornners for the windows and xmobar WITHOUT using a picom fork |
| 2022-10-28 23:09:49 +0200 | <geekosaur> | nope |
| 2022-10-28 23:10:22 +0200 | <geekosaur> | xmonad uses old-style window borders, they're boringly square and depth 1 |
| 2022-10-28 23:16:13 +0200 | Guest7732 | (~Guest77@109.98.214.166) (Quit: Client closed) |
| 2022-10-28 23:35:12 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::f30b) (Ping timeout: 250 seconds) |
| 2022-10-28 23:56:59 +0200 | mvk | (~mvk@2607:fea8:5ce3:8500::f30b) |
