2021-10-24 00:01:10 +0200 | catman | (~catman@user/catman) |
2021-10-24 00:42:00 +0200 | cyr4x3 | (~cyr4x3@139.47.115.87) |
2021-10-24 00:43:13 +0200 | catman | (~catman@user/catman) (Ping timeout: 244 seconds) |
2021-10-24 00:44:15 +0200 | benin | (~benin@183.82.207.116) (Ping timeout: 244 seconds) |
2021-10-24 00:44:46 +0200 | benin | (~benin@183.82.207.116) |
2021-10-24 00:45:44 +0200 | catman | (~catman@user/catman) |
2021-10-24 00:54:17 +0200 | cyr4x3 | (~cyr4x3@139.47.115.87) (Quit: WeeChat 2.3) |
2021-10-24 01:43:40 +0200 | mvk | (~mvk@2607:fea8:5cc1:300::4b63) |
2021-10-24 01:59:58 +0200 | seschwar | (~seschwar@user/seschwar) (Quit: :wq) |
2021-10-24 02:16:52 +0200 | mariari | (~mariari@user/mariari) |
2021-10-24 02:21:26 +0200 | <mariari> | has anyone experienced xmonad locking up horribly when a program demands constant focus? I've notice with some wine games and other applications that this could happen, causing xmonad to spasm shifting the boarder color of the application between the focus and unfcous state. When the application stops, these inputs are buffered and the machine becomes unusable for a while after this |
2021-10-24 02:27:47 +0200 | <L29Ah> | mariari: no |
2021-10-24 02:27:53 +0200 | <L29Ah> | but i use wine's virtual desktop feature |
2021-10-24 02:28:02 +0200 | <L29Ah> | 10/10 do recommend |
2021-10-24 02:29:16 +0200 | <mariari> | It's not just wine sadly, it seems any application that seems to demand attention in a certain way it freaks xmonad out, I can't find any bug reports of a similar problem |
2021-10-24 02:29:36 +0200 | <L29Ah> | can you name a few? |
2021-10-24 02:29:44 +0200 | <mariari> | Games mostly |
2021-10-24 02:29:57 +0200 | <L29Ah> | don't see that with xonotic |
2021-10-24 02:30:01 +0200 | <mariari> | not all games |
2021-10-24 02:30:04 +0200 | <mariari> | xonotic does not have the issue |
2021-10-24 02:30:14 +0200 | <mariari> | it's only certain applications that demand the screen attention in certain ways |
2021-10-24 02:30:58 +0200 | <mariari> | it's with how certain games do a call, most games do it in a way that does not freak out xmonad |
2021-10-24 02:42:31 +0200 | <geekosaur> | this may be improved with the new ewmh (which is still being ironed out), we don't currently advertise that we handle focus changes correctly and this confuses a number of applications |
2021-10-24 02:42:47 +0200 | <mariari> | ahh is that what may be causing this? |
2021-10-24 02:43:25 +0200 | <geekosaur> | some of the apps that do it have options to force old-style focus changing, and they behave correctly in that case. (I think vlc is one?) |
2021-10-24 02:45:58 +0200 | <geekosaur> | so hopefully when we get 0.17 out (should be soon) this should be mostly fixed. if it isn't, open an issue then |
2021-10-24 02:46:02 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
2021-10-24 02:46:48 +0200 | <mariari> | OK, do you know the rough behavior I'm alluding to? I just recorded an application that does it |
2021-10-24 02:46:55 +0200 | <geekosaur> | (we're targeting before the end of the month. how "before" remains to be seen) |
2021-10-24 02:46:59 +0200 | <mariari> | it makes xmonad fairly unusable |
2021-10-24 02:47:07 +0200 | <mariari> | ahh nice, I hope it ends up on the stack lts soon, as that's how I use xmonad |
2021-10-24 02:47:23 +0200 | <geekosaur> | the focus flickering thing is fairly well known, yes |
2021-10-24 02:47:46 +0200 | <geekosaur> | it's a largeish part of why the ewmh revamp that is still in progress |
2021-10-24 02:51:38 +0200 | <geekosaur> | …and there may still be breakage afterward from apps that ignored the part of ewmh that says that a window manager is not required to obey application-initiated focus changes, but we can hope those are few (and default will be to honor them, it'll be configurable) |
2021-10-24 03:01:00 +0200 | <mariari> | do you know the specific name for the event that causes this? |
2021-10-24 03:06:20 +0200 | <geekosaur> | _NET_ACTIVE_WINDOW |
2021-10-24 03:08:28 +0200 | <geekosaur> | hm, actually I'm not exactly sure we handle it if an app just calls XSetInputFocus directly, we may just slap it back to what we think it should be |
2021-10-24 03:08:44 +0200 | <geekosaur> | apps are not supposed to call that directly except specifically to their own subwindows |
2021-10-24 03:09:24 +0200 | <geekosaur> | which is why _NET_ACTIVE_WINDOW exists, to allow apps to request that the wm change focus |
2021-10-24 03:19:46 +0200 | benin | (~benin@183.82.207.116) (Ping timeout: 244 seconds) |
2021-10-24 03:20:48 +0200 | <mariari> | I see, so if that gets called often hence the boarder flickering and xmonad lag/unresposiveness |
2021-10-24 03:22:12 +0200 | <geekosaur> | well, some apps just get uppity if they change focus and then something else (like the window manager) changes it somewhere else, so they change it again |
2021-10-24 03:22:20 +0200 | <geekosaur> | and you end up with an ugly loop |
2021-10-24 03:23:27 +0200 | benin | (~benin@183.82.207.116) |
2021-10-24 03:23:37 +0200 | <mariari> | but what if it's just 1 application stealing focus? |
2021-10-24 03:23:42 +0200 | <mariari> | that is what I have at least |
2021-10-24 03:23:52 +0200 | <mariari> | probably calling it constantly so it flickers on 1 window |
2021-10-24 03:24:29 +0200 | <geekosaur> | right, 1 app changes focus to itself, xmonad changes it back, app changes it bvack to itself, lather rinse repeat |
2021-10-24 03:24:41 +0200 | <mariari> | changes it back to where exactly? |
2021-10-24 03:24:48 +0200 | <mariari> | that is the confusing part for me |
2021-10-24 03:24:57 +0200 | <mariari> | as you can have the item focused, and then the next moment it works like that |
2021-10-24 03:25:03 +0200 | <mariari> | so I'm unsure of where the focus is moving to |
2021-10-24 03:25:12 +0200 | <geekosaur> | to whatever window had focus before the app forcibly changed it |
2021-10-24 03:25:45 +0200 | <geekosaur> | if this is happening while the app has focus then you're seeing the reverse form iof it, some app is stealing focus and then xmonad sets it back to your app |
2021-10-24 03:25:55 +0200 | <geekosaur> | you still get the loop |
2021-10-24 03:26:22 +0200 | <geekosaur> | alternately you can have two apps fighting over which one shoyuld get focxus and stealing it from each other |
2021-10-24 03:26:23 +0200 | <mariari> | well I have an example where in a menu the game does not steal focus, so the game is focused, then when I close the windows it acts like that |
2021-10-24 03:26:26 +0200 | <geekosaur> | *focus |
2021-10-24 03:26:32 +0200 | <mariari> | so it's one app steal focus from itself it seems |
2021-10-24 03:27:46 +0200 | <geekosaur> | hm. either (1) this is the not-fully-supporting ewmh thing, or (2) we've once seen an app that behaved or not depending on whether a compositor was running or not |
2021-10-24 03:27:56 +0200 | <geekosaur> | notably that one also involved menus |
2021-10-24 03:28:03 +0200 | <geekosaur> | (and it was a game design app) |
2021-10-24 03:28:54 +0200 | <mariari> | huh a compositor could effect it, I could perhaps put on whatever compoton is called these days to see if that makes a difference |
2021-10-24 03:28:59 +0200 | <mariari> | I think it's likely 1) |
2021-10-24 03:29:02 +0200 | <geekosaur> | picom, apparently |
2021-10-24 03:29:16 +0200 | <mariari> | as I've launched the game on stumpwm, and it didn't freak out but it stole attention every time I tried to go away |
2021-10-24 03:29:37 +0200 | <geekosaur> | although I just run compton because (a) that's what's packaged on ubuntu (b) I keep hearing about performance problems with picom |
2021-10-24 03:31:03 +0200 | <geekosaur> | ok, so that's actually the same issue but stumpwm apparently handles it better than we do, or maybe that's because of our not advertising _NET_ACTIVE_WINDOW |
2021-10-24 03:31:49 +0200 | <geekosaur> | again I'd be interested in hearing of the ewmh fixes in 0.17 help or even just change the behavior |
2021-10-24 03:32:04 +0200 | <geekosaur> | *if the |
2021-10-24 03:32:07 +0200 | <mariari> | yeah even it just making it not make xmonad unusable if it lasts for any length of time is great |
2021-10-24 03:32:20 +0200 | <mariari> | yesterday I had it switch between workspace 2 and 3 for a solid 10 minutes before I killed my entire x11 |
2021-10-24 03:32:33 +0200 | <geekosaur> | they're not complete yet so I can't even point you at a PR to install locally |
2021-10-24 03:38:43 +0200 | <mariari> | yeah that's fine, hopefully it'll be on an lts eventually |
2021-10-24 03:40:02 +0200 | <mariari> | with this particular application I hope to get it's call fixed, so it'll be hard to tell if the game fixes it as I can't save an older version sadly |
2021-10-24 03:41:17 +0200 | <mariari> | I wish I had better examples for this, I only do for the other bugs I face |
2021-10-24 03:43:38 +0200 | <mariari> | there is a fun one with windows that close bringing focus to the last window in the stack, so in a sub layout with tabs where one has a tab in the last slot in the stack it moves to the non visible one |
2021-10-24 03:50:14 +0200 | catman | (~catman@user/catman) (Ping timeout: 265 seconds) |
2021-10-24 03:51:54 +0200 | catman | (~catman@user/catman) |
2021-10-24 04:03:10 +0200 | banc | (banc@gateway/vpn/airvpn/banc) (Ping timeout: 244 seconds) |
2021-10-24 04:22:09 +0200 | banc | (banc@gateway/vpn/airvpn/banc) |
2021-10-24 04:38:49 +0200 | td_ | (~td@muedsl-82-207-238-090.citykom.de) (Ping timeout: 244 seconds) |
2021-10-24 04:40:49 +0200 | td_ | (~td@muedsl-82-207-238-060.citykom.de) |
2021-10-24 05:21:40 +0200 | mvk | (~mvk@2607:fea8:5cc1:300::4b63) (Ping timeout: 252 seconds) |
2021-10-24 08:03:42 +0200 | benin5 | (~benin@183.82.207.116) |
2021-10-24 08:06:05 +0200 | benin | (~benin@183.82.207.116) (Ping timeout: 260 seconds) |
2021-10-24 08:06:05 +0200 | benin5 | benin |
2021-10-24 09:49:14 +0200 | ircbrowse_tom | (~ircbrowse@2a01:4f8:1c1c:9319::1) |
2021-10-24 09:49:19 +0200 | Server | +cnt |
2021-10-24 09:56:43 +0200 | darkstarx | (~darkstard@2601:1c2:300:c8a0::6c32) (Remote host closed the connection) |
2021-10-24 09:57:03 +0200 | darkstarx | (~darkstard@2601:1c2:300:c8a0::6c32) |
2021-10-24 11:05:31 +0200 | <liskin> | hm, this endless flicker issue was historically known as https://code.google.com/archive/p/xmonad/issues/200 and I haven't seen it in years… |
2021-10-24 11:06:32 +0200 | <liskin> | mariari, geekosaur: it's also worth noting that all the changes related to EWMH that we wanted to do before the 0.17 release are already in |
2021-10-24 11:07:12 +0200 | <liskin> | what is left is just a revamp of the user/configuration interface of the EWMH modules, but functionally we're good already |
2021-10-24 11:07:59 +0200 | <liskin> | Solid: did we decide what to do with the X.L.Fullscreen deprecation warning? |
2021-10-24 11:24:04 +0200 | seschwar | (~seschwar@user/seschwar) |
2021-10-24 12:37:07 +0200 | humky | (~humky@user/humky) (Quit: Leaving) |
2021-10-24 13:57:04 +0200 | eqw | (~eqw@31.134.178.99) |
2021-10-24 14:44:15 +0200 | mc47 | (~mc47@xmonad/TheMC47) |
2021-10-24 15:37:52 +0200 | <Solid> | liskin: we did not and I still don't quite know how to feel about it |
2021-10-24 15:38:43 +0200 | <Solid> | btw, did you self assign 341 because you don't want anyone else to interfer or because you'll do it if no one else does? :) |
2021-10-24 15:55:24 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
2021-10-24 15:55:32 +0200 | catman | (~catman@user/catman) (Remote host closed the connection) |
2021-10-24 15:58:00 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
2021-10-24 16:12:04 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
2021-10-24 16:23:38 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Quit: Leaving) |
2021-10-24 16:26:43 +0200 | catman | (~catman@user/catman) |
2021-10-24 16:34:51 +0200 | <liskin> | Dunno what's 341 (on a walk) but definitely the latter |
2021-10-24 16:34:58 +0200 | <liskin> | Solid: ^ |
2021-10-24 16:35:58 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
2021-10-24 16:36:04 +0200 | <liskin> | I'm working on packdeps today, then then announcement and/or ppPrinters |
2021-10-24 16:36:06 +0200 | <Solid> | aight, thanks! (it's the "update contributing" issue) |
2021-10-24 16:37:37 +0200 | <liskin> | Oh, then that's a bit of both. I have some thoughts that I wanted to get out in writing but that doesn't mean I need to do the whole revamp |
2021-10-24 16:48:16 +0200 | <Solid> | aight, I'll do some of the menial things then (like deleting config and migrating style) |
2021-10-24 16:50:37 +0200 | benin8 | (benin@gateway/vpn/protonvpn/benin) |
2021-10-24 16:52:50 +0200 | benin | (~benin@183.82.207.116) (Ping timeout: 260 seconds) |
2021-10-24 16:52:51 +0200 | benin8 | benin |
2021-10-24 17:10:43 +0200 | <liskin> | Thx |
2021-10-24 17:12:05 +0200 | <liskin> | I mean, feel free to do it all if you want, I'll just make sure it says what I want it to say |
2021-10-24 17:14:35 +0200 | <Solid> | sure, I'll do as much as I can before PnP later this evening |
2021-10-24 17:18:49 +0200 | benin8 | (benin@gateway/vpn/protonvpn/benin) |
2021-10-24 17:21:50 +0200 | benin | (benin@gateway/vpn/protonvpn/benin) (Ping timeout: 258 seconds) |
2021-10-24 17:21:51 +0200 | benin8 | benin |
2021-10-24 17:34:37 +0200 | <liskin> | What's PnP? |
2021-10-24 17:38:14 +0200 | benin5 | (~benin@183.82.207.116) |
2021-10-24 17:38:56 +0200 | benin | (benin@gateway/vpn/protonvpn/benin) (Remote host closed the connection) |
2021-10-24 17:38:56 +0200 | benin5 | benin |
2021-10-24 17:42:01 +0200 | <Solid> | pen and paper (think DnD, but a different system (we play call of cthulu)) |
2021-10-24 17:43:59 +0200 | <liskin> | I see |
2021-10-24 18:06:40 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
2021-10-24 18:07:03 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) (Remote host closed the connection) |
2021-10-24 18:12:52 +0200 | benin4 | (~benin@106.198.88.230) |
2021-10-24 18:15:07 +0200 | benin | (~benin@183.82.207.116) (Ping timeout: 258 seconds) |
2021-10-24 18:15:08 +0200 | benin4 | benin |
2021-10-24 18:20:11 +0200 | benin | (~benin@106.198.88.230) (Read error: Connection reset by peer) |
2021-10-24 18:22:04 +0200 | benin | (~benin@183.82.207.116) |
2021-10-24 18:22:28 +0200 | qbt | (~qbt@user/edun) |
2021-10-24 20:44:05 +0200 | humky | (~humky@user/humky) |
2021-10-24 21:17:00 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
2021-10-24 21:24:12 +0200 | qbt | (~qbt@user/edun) (Quit: Leaving.) |
2021-10-24 22:19:17 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection) |
2021-10-24 22:20:13 +0200 | humky | (~humky@user/humky) (Quit: Leaving) |
2021-10-24 22:21:19 +0200 | rekahsoft | (~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) |
2021-10-24 22:36:26 +0200 | seiryn | (~seiryn@2a01cb040147e000baac7520288c550c.ipv6.abo.wanadoo.fr) |
2021-10-24 22:40:12 +0200 | catman | (~catman@user/catman) (Ping timeout: 244 seconds) |
2021-10-24 22:40:20 +0200 | catman_ | (~catman@user/catman) |
2021-10-24 22:40:52 +0200 | catman_ | catman |
2021-10-24 22:40:52 +0200 | geekosaur | (~geekosaur@xmonad/geekosaur) |
2021-10-24 22:47:11 +0200 | seiryn | (~seiryn@2a01cb040147e000baac7520288c550c.ipv6.abo.wanadoo.fr) (Quit: WeeChat 3.3) |
2021-10-24 22:48:17 +0200 | seiryn | (~seiryn@2a01cb040147e000baac7520288c550c.ipv6.abo.wanadoo.fr) |
2021-10-24 23:09:54 +0200 | seiryn | (~seiryn@2a01cb040147e000baac7520288c550c.ipv6.abo.wanadoo.fr) (Quit: WeeChat 3.3) |
2021-10-24 23:14:37 +0200 | <jakefromstatefar> | Whenever my mumble client's tiled, if it gets resized, it unmaps, and is incapable of re-showing itself. |
2021-10-24 23:14:48 +0200 | <jakefromstatefar> | The same thing happens if I switch workspaces. |
2021-10-24 23:15:01 +0200 | <jakefromstatefar> | Does anyone know why? |
2021-10-24 23:19:04 +0200 | mc47 | (~mc47@xmonad/TheMC47) (Remote host closed the connection) |
2021-10-24 23:24:58 +0200 | <L29Ah> | worksforme |
2021-10-24 23:25:31 +0200 | <jakefromstatefar> | Hm, maybe it's nixes fault |
2021-10-24 23:25:33 +0200 | <L29Ah> | try disabling stuff in User Interface setting |
2021-10-24 23:25:46 +0200 | <L29Ah> | > Always On Top |
2021-10-24 23:25:46 +0200 | <L29Ah> | looks sus |
2021-10-24 23:25:47 +0200 | <lambdabot> | error: |
2021-10-24 23:25:47 +0200 | <lambdabot> | Data constructor not in scope: Always :: t0 -> t1 -> terror: |
2021-10-24 23:25:47 +0200 | <lambdabot> | • Data constructor not in scope: On |
2021-10-24 23:29:14 +0200 | <jakefromstatefar> | Nix isn't entirely the problem, but having overlay enabled is wacky |
2021-10-24 23:30:27 +0200 | <jakefromstatefar> | Changing workspaces still causes it to hide, but it returns when requested |
2021-10-24 23:30:32 +0200 | <L29Ah> | ah, i never used the overlay |
2021-10-24 23:30:49 +0200 | <L29Ah> | i think you should tell xmonad not to touch the overlay |
2021-10-24 23:31:48 +0200 | <jakefromstatefar> | It doesn't even show up XD |
2021-10-24 23:31:55 +0200 | <jakefromstatefar> | I'll just leave it disabled, I guess |
2021-10-24 23:32:01 +0200 | <L29Ah> | btw https://github.com/l29ah/xmonad-config/blob/master/xmonad.hs#L79-L103 does this belong in xmonad-contrib? |
2021-10-24 23:32:06 +0200 | <L29Ah> | liskin: ^ |
2021-10-24 23:32:16 +0200 | <L29Ah> | pulls dbus |
2021-10-24 23:33:10 +0200 | <geekosaur> | dbus probably makes it -extras |
2021-10-24 23:35:31 +0200 | <jakefromstatefar> | Is there a way to make `XMonad.Layout.Hidden` work across workspaces? |
2021-10-24 23:36:04 +0200 | <jakefromstatefar> | Currently, it only functions on a per-workspace basis. |
2021-10-24 23:37:08 +0200 | <jakefromstatefar> | What I desire is: e.g - I hide/minimize window A on ws A, then try to unhide/unminimize on ws B, window A should appear. |
2021-10-24 23:37:28 +0200 | <L29Ah> | https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Layout-BoringWindows.html wtf is this |
2021-10-24 23:37:40 +0200 | <L29Ah> | zero info in the docs on the actual impact on UI |
2021-10-24 23:38:12 +0200 | <geekosaur> | L29Ah, it's best explained by the modules that use it, I think |
2021-10-24 23:38:38 +0200 | <L29Ah> | that i need to grep, i guess :/ |
2021-10-24 23:38:43 +0200 | <geekosaur> | jakefromstatefar, layout state only exists within a workspace |
2021-10-24 23:39:14 +0200 | <geekosaur> | it would have to be redesigned to put the stack in XS instead of in the layout to work across workspaces like that |
2021-10-24 23:39:57 +0200 | <geekosaur> | anyway a window marked boring can be auto-skipped by various move commands that are aware of the BoringWindows module |
2021-10-24 23:40:14 +0200 | <geekosaur> | otherwise it has no effect |
2021-10-24 23:41:35 +0200 | <jakefromstatefar> | boringWindows gives abilities to skip over windows marked as `boring` |
2021-10-24 23:41:51 +0200 | <jakefromstatefar> | It doesn't work well with tabs |
2021-10-24 23:42:00 +0200 | <jakefromstatefar> | Which's why I switched to `hidden` |
2021-10-24 23:47:34 +0200 | <jakefromstatefar> | So, for 0.17, it looks like the only thing left is misc documentation/versioning/information updating, right? |
2021-10-24 23:47:55 +0200 | <jakefromstatefar> | Are we going to merge some of my screenshots into xmonad-web? |
2021-10-24 23:48:21 +0200 | <geekosaur> | no idea |
2021-10-24 23:53:32 +0200 | <jakefromstatefar> | On another note: https://termbin.com/ogeb -- thoughts? |
2021-10-24 23:53:50 +0200 | <jakefromstatefar> | It's a start to my version of the tree-structure proposal. |
2021-10-24 23:56:18 +0200 | <liskin> | jakefromstatefar: "slotThe added this to the v0.17.1 milestone yesterday" at the bottom of https://github.com/xmonad/xmonad-contrib/issues/160 suggests that we aren't hoping to merge the screenshots before the 0.17.0 release, but would be nice to do it after |
2021-10-24 23:56:37 +0200 | <liskin> | I must say that I'm sooo looking forward to a little holiday though :-) |
2021-10-24 23:56:54 +0200 | <liskin> | (yeah I know it's not been that long since my last one, but it's been quite a crunch now) |