IRCBrowse

2022/10/14

2022-10-14 00:09:47 +0200stackdroid18(14094@user/stackdroid) (Quit: hasta la vista... tchau!)
2022-10-14 00:14:26 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130)
2022-10-14 00:50:12 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130) (Ping timeout: 264 seconds)
2022-10-14 02:09:51 +0200werneta(~werneta@137.78.30.207) (Ping timeout: 260 seconds)
2022-10-14 02:53:35 +0200logzet_(~quassel@2001:9e8:e50c:ca00:dabb:c1ff:fed3:a1b9)
2022-10-14 02:53:48 +0200logzet(~quassel@2001:9e8:e53b:9500:dabb:c1ff:fed3:a1b9) (Ping timeout: 264 seconds)
2022-10-14 02:56:42 +0200ghormoon(~ghormoon@ghorland.net) (Ping timeout: 268 seconds)
2022-10-14 03:07:12 +0200xtayex(~xtayex@n119236109098.netvigator.com)
2022-10-14 03:16:15 +0200xtayexxTayEx
2022-10-14 03:16:43 +0200xTayExxtayex
2022-10-14 03:32:07 +0200logzet_(~quassel@2001:9e8:e50c:ca00:dabb:c1ff:fed3:a1b9) (Ping timeout: 246 seconds)
2022-10-14 03:33:35 +0200ghormoon(~ghormoon@ghorland.net)
2022-10-14 03:38:21 +0200xtayex1(~xtayex@219.228.146.174)
2022-10-14 03:38:53 +0200xtayex(~xtayex@n119236109098.netvigator.com) (Quit: Client closed)
2022-10-14 03:49:36 +0200ghormoon(~ghormoon@ghorland.net) (Ping timeout: 260 seconds)
2022-10-14 03:58:59 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-10-14 04:03:36 +0200banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 260 seconds)
2022-10-14 04:16:26 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 260 seconds)
2022-10-14 04:23:49 +0200banc(banc@gateway/vpn/airvpn/banc)
2022-10-14 04:27:49 +0200td_(~td@83.135.9.55) (Ping timeout: 252 seconds)
2022-10-14 04:29:36 +0200td_(~td@83.135.9.35)
2022-10-14 04:30:18 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-10-14 04:40:00 +0200ghormoon(~ghormoon@ghorland.net)
2022-10-14 04:45:40 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1) (Quit: The Lounge - https://thelounge.chat)
2022-10-14 04:48:15 +0200terrorjack(~terrorjac@2a01:4f8:1c1e:509a::1)
2022-10-14 05:10:29 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 268 seconds)
2022-10-14 05:11:39 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-10-14 05:57:17 +0200xtayex1(~xtayex@219.228.146.174) (Ping timeout: 252 seconds)
2022-10-14 06:25:39 +0200xtayex1(~xtayex@219.228.146.174)
2022-10-14 06:25:56 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 260 seconds)
2022-10-14 06:52:51 +0200xtayex1(~xtayex@219.228.146.174) (Ping timeout: 268 seconds)
2022-10-14 07:16:41 +0200fjMSX(~hypni2p@2.92.213.55) (Remote host closed the connection)
2022-10-14 07:20:41 +0200chomwitt(~chomwitt@2a02:587:dc0c:c200:b1b7:d42d:7f9d:2308)
2022-10-14 07:21:02 +0200wusticality(~user@76.131.115.3) (Remote host closed the connection)
2022-10-14 07:25:16 +0200wusticality(~user@76.131.115.3)
2022-10-14 07:27:30 +0200 <xmonadtrack> xmonad-contrib exorcist365 {Tony Zorman} * v0.17.1-36-g4734551c: X.H.Modal: Remove `Keys` type alias (22 hours ago, 1 file, 5+ 9-) https://github.com/xmonad/xmonad-contrib/commit/4734551c76b9
2022-10-14 07:27:30 +0200 <xmonadtrack> xmonad-contrib Tony Zorman {GitHub} * v0.17.1-37-g7d4f0aae: Merge pull request #761 from exorcist365/master (3 minutes ago, 0 files, 0+ 0-) https://github.com/xmonad/xmonad-contrib/commit/7d4f0aaece8c
2022-10-14 07:27:44 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-10-14 07:27:51 +0200fjMSX(~hypni2p@2.92.213.55)
2022-10-14 07:28:56 +0200ghormoon(~ghormoon@ghorland.net) (Ping timeout: 260 seconds)
2022-10-14 07:54:18 +0200ft(~ft@p3e9bc57b.dip0.t-ipconnect.de) (Quit: leaving)
2022-10-14 08:20:08 +0200ghormoon(~ghormoon@ghorland.net)
2022-10-14 08:32:55 +0200logzet(~quassel@2001:9e8:e50c:ca00:dabb:c1ff:fed3:a1b9)
2022-10-14 08:51:11 +0200xtayex1(~xtayex@180.160.67.85)
2022-10-14 08:55:07 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds)
2022-10-14 08:58:01 +0200fjMSX(~hypni2p@2.92.213.55) (Remote host closed the connection)
2022-10-14 09:01:04 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2022-10-14 09:13:30 +0200Guest12(~Guest12@160.119.238.207)
2022-10-14 09:14:04 +0200Guest12(~Guest12@160.119.238.207) (Client Quit)
2022-10-14 09:15:11 +0200wusticality(~user@76.131.115.3) (Remote host closed the connection)
2022-10-14 09:45:58 +0200diep(~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c)
2022-10-14 10:09:01 +0200aliosablack(~chomwitt@2a02:587:dc0c:c200:b1b7:d42d:7f9d:2308)
2022-10-14 10:09:34 +0200chomwitt(~chomwitt@2a02:587:dc0c:c200:b1b7:d42d:7f9d:2308) (Read error: Connection reset by peer)
2022-10-14 11:00:18 +0200liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2022-10-14 11:10:46 +0200diep(~diep@2a01:cb11:2d7:4a00:a13f:e40c:c4e8:736c) (Ping timeout: 268 seconds)
2022-10-14 11:10:46 +0200diep_(~diep@92.138.126.124)
2022-10-14 11:14:49 +0200sagax(~sagax_nb@user/sagax)
2022-10-14 11:36:03 +0200xtayex1(~xtayex@180.160.67.85) (Ping timeout: 268 seconds)
2022-10-14 11:48:44 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130)
2022-10-14 11:55:47 +0200cfricke(~cfricke@user/cfricke)
2022-10-14 12:17:11 +0200fjMSX(~hypni2p@2.92.213.55)
2022-10-14 12:22:16 +0200xtayex1(~xtayex@180.160.67.85)
2022-10-14 14:22:31 +0200Ehllie(~Thunderbi@217-67-208-66.itsa.net.pl)
2022-10-14 14:30:00 +0200ircbrowse_tom(~ircbrowse@2a01:4f8:1c1c:9319::1)
2022-10-14 14:30:05 +0200Server+cnt
2022-10-14 14:43:05 +0200xtayex1(~xtayex@180.160.67.85) (Ping timeout: 252 seconds)
2022-10-14 14:47:33 +0200ircbrowse_tom(~ircbrowse@static.162.49.55.162.clients.your-server.de)
2022-10-14 14:47:36 +0200Server+cnt
2022-10-14 14:55:07 +0200ircbrowse_tom(~ircbrowse@2a01:4f8:1c1c:9319::1)
2022-10-14 14:55:10 +0200Server+cnt
2022-10-14 15:08:16 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130) (Ping timeout: 246 seconds)
2022-10-14 15:09:50 +0200xtayex1(~xtayex@180.160.67.85)
2022-10-14 15:34:03 +0200xmonadtrack(~xmonadtra@xmonad/geekosaur) (Remote host closed the connection)
2022-10-14 15:34:27 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2022-10-14 15:39:30 +0200jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2022-10-14 15:54:13 +0200Ehllie(~Thunderbi@217-67-208-66.itsa.net.pl) (Ping timeout: 252 seconds)
2022-10-14 16:13:07 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-10-14 16:23:20 +0200ml|_(~ml|@user/ml/x-5298235) (Ping timeout: 268 seconds)
2022-10-14 16:24:37 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2022-10-14 16:24:37 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2022-10-14 16:24:37 +0200xmonadtrack(~xmonadtra@xmonad/geekosaur)
2022-10-14 16:36:54 +0200ml|_(~ml|@user/ml/x-5298235)
2022-10-14 17:07:49 +0200ft(~ft@p3e9bc57b.dip0.t-ipconnect.de)
2022-10-14 17:21:56 +0200MrElendig(~Urist@archlinux/op/MrElendig) (Quit: nuking a hurricane)
2022-10-14 17:23:07 +0200MrElendig(~Urist@archlinux/op/MrElendig)
2022-10-14 17:23:52 +0200diep_(~diep@92.138.126.124) (Remote host closed the connection)
2022-10-14 17:34:39 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.7)
2022-10-14 17:34:51 +0200 <T_X> hi, does anyone have an example code snippet on how to use XMonad.Layout.Stoppable for specific workspaces only?
2022-10-14 17:35:10 +0200liskin[m](~liskinmat@2001:470:69fc:105::768)
2022-10-14 17:36:54 +0200 <T_X> also, does it work fine with Firefox on a per window basis? that is if I have one Firefox window on a specific workspace which I want to stay active for webchats and their notifications. while other Firefox windows on other workspaces should stay stoppable
2022-10-14 17:37:37 +0200 <T_X> or would I need an extra Firefox profile (and by that dedicated process?) for this Firefox window with the webchats?
2022-10-14 17:47:21 +0200 <geekosaur> you would have to check what _NET_WM_PID property is for each window. I think Firefox already uses a process per window though (possibly per tab in which case it won't work well unless you stick to one tab per window)
2022-10-14 17:49:15 +0200 <geekosaur> for a particular workspace you'd do something like https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L144 but have `stoppable` in place of `avoidStrutsOn []`
2022-10-14 17:51:12 +0200 <geekosaur> or perhaps in your case the reverse, don't use stoppable on that workspace and then use stoppable after it (not so different from what I did with avoidStruts, see just below the avoidStrutsOn line)
2022-10-14 17:59:09 +0200 <geekosaur> I don't know that that layout has been tested with recent versions of firefox, since they do similar things to chromium these days and it says it doesn't work with chromium
2022-10-14 18:00:09 +0200 <geekosaur> Stoppable is pretty hackym if the process that needs to be stopped isn't reported by _NET_WM_PID then it won't work
2022-10-14 18:18:19 +0200xtayex1(~xtayex@180.160.67.85) (Ping timeout: 252 seconds)
2022-10-14 19:04:15 +0200aliosablack(~chomwitt@2a02:587:dc0c:c200:b1b7:d42d:7f9d:2308) (Ping timeout: 268 seconds)
2022-10-14 19:12:22 +0200 <Solid> (but that goes for a lot of functionality offered by all kinds of modules)
2022-10-14 19:33:32 +0200geekosaurgonna disappear to do battle with cabal again (which will blow away xmonad since it's cabal-installed…)
2022-10-14 19:33:56 +0200 <geekosaur> (testing/debugging new XDG support so old cabal store etc. goes away)
2022-10-14 19:34:11 +0200geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2022-10-14 19:34:24 +0200xmonadtrack(~xmonadtra@xmonad/geekosaur) (Remote host closed the connection)
2022-10-14 19:43:46 +0200 <T_X> geekosaur[m]: thanks for the reply!
2022-10-14 19:44:25 +0200geekosaur(~geekosaur@xmonad/geekosaur)
2022-10-14 19:46:30 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2022-10-14 19:46:30 +0200xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2022-10-14 19:46:30 +0200xmonadtrack(~xmonadtra@xmonad/geekosaur)
2022-10-14 19:49:16 +0200 <geekosaur> welp, that was fast
2022-10-14 19:49:25 +0200 <geekosaur> I now have two bugs in cabal HEAD 🙂
2022-10-14 20:13:53 +0200 <T_X> hm, so far the stoppable does not quite seem to work for me. even if I use it like "xmonad $ ewmh defaultConfig { ..., layoutHook = Full ||| stoppable Full"
2022-10-14 20:15:01 +0200 <T_X> that is I don't see anything changing to "T" in "ps aux", even after the necessary 15 seconds timeout
2022-10-14 20:15:01 +0200 <geekosaur> then firefox probably doesn't work the right way any more
2022-10-14 20:15:26 +0200 <T_X> but also for instance the quasselclient (an GUI IRC client) does not seem to stop
2022-10-14 20:16:02 +0200 <geekosaur> can you check its _NET_WM_PID property?
2022-10-14 20:16:50 +0200 <geekosaur> `sleep 5; xprop _NET_WM_PID` in a terminal, then switch to the workspace with the quasselclient window, wait for the cursor to change to a crosshair, and click the quasselclient window
2022-10-14 20:19:26 +0200 <T_X> $ sleep 5; xprop _NET_WM_PID -> _NET_WM_PID(CARDINAL) = 4786 \\ ps aux | grep quassel | grep -v grep -> "myuser 4786 0.0 0.5 1831240 79808 pts/2 SNl Sep28 8:35 quasselclient"
2022-10-14 20:24:00 +0200 <geekosaur> do you have an environment variable $HOST set? if not, it assumes a remote window
2022-10-14 20:24:57 +0200 <geekosaur> or use XMonad.Util.RemoteWindows.manageRemote to look up and store the hostname (https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Util-RemoteWindows.html#v:ma…)
2022-10-14 20:25:47 +0200 <geekosaur> (yes, X11 supports remote windows. usually this is disabled for security reasons but Stoppable still checks for it and refuses to operate if the window might be remote)
2022-10-14 20:27:05 +0200 <T_X> geekosaur: ah, yes, seems like quasselclient does not have $HOST set: cat /proc/4786/environ | grep HOST -> empty, exit 1
2022-10-14 20:27:23 +0200 <T_X> hm, in my zsh I have $HOST set though
2022-10-14 20:28:00 +0200 <geekosaur> well, it's xmonad that needs HOST set, and it has to be set when X11 starts not merely in a terminal (only Fedora reads your dotfiles when setting up an X session)
2022-10-14 20:28:36 +0200 <geekosaur> so check environ for the xmonad-x86_64-linux (or etc.) process
2022-10-14 20:29:04 +0200 <geekosaur> also check `xprop WM_CLIENT_MACHINE` for quasselclient the same way I showed for _NET_WMPID
2022-10-14 20:30:31 +0200 <geekosaur> fwiw on debian/ubuntu I now use https://github.com/geekosaur/xmonad.hs/blob/skkukuk/10profile in /etc/X11/Xsession.d; something similar might work for other systems
2022-10-14 20:31:21 +0200 <T_X> ps -Af | grep xmonad | grep -v "grep" -> "myuser 3743 3712 0 Sep28 ? 00:15:57 /home/linus/.xmonad/xmonad-x86_64-linux"; cat /proc/3743/environ| grep HOST -> empty/exit1
2022-10-14 20:32:16 +0200 <T_X> xprop WM_CLIENT_MACHINE [on quasselclient window] -> WM_CLIENT_MACHINE(STRING) = "myuser-work"; same as in /etc/hostname
2022-10-14 20:32:27 +0200justHauntedffffffradiofree
2022-10-14 20:32:48 +0200ffffffradiofreejusFffffffradiof
2022-10-14 20:32:52 +0200 <geekosaur> okay, so you need to either set $HOST where it'll be found by X11 startup, or use manageRemote hook I pointed to earlier to look up the hostname dynamically
2022-10-14 20:33:46 +0200 <geekosaur> (getHostName as shown in the example requires Network.BSD import)
2022-10-14 20:36:43 +0200geekosaurwonders if it should just assume local host if host etc. isn't set, since nobody much uses remote any more
2022-10-14 20:40:49 +0200 <T_X> I've added this diff: https://gist.github.com/T-X/c0b4834f55c0ee870b0e9650750befc5. installed the libghc-network-bsd-dev package. and recompiled+restarted xmonad. would I need to restart even more things?
2022-10-14 20:42:17 +0200 <geekosaur> the quassel client probably since it needs to go through the manageHook for the window to be registered as local
2022-10-14 20:42:31 +0200 <geekosaur> I would hope it then does the right thing
2022-10-14 20:47:34 +0200 <T_X> hm, $ ps aux | grep quassel | grep -v grep -> myuser 3275793 0.3 1.1 1789296 182228 pts/7 SNl 20:43 0:00 quasselclient
2022-10-14 20:47:41 +0200 <T_X> still an "S" instead of a "T"
2022-10-14 20:48:14 +0200 <geekosaur> you should be able to check that by looking at the XMONAD_REMOTE property of the quasselclient same way you looked at the other two props
2022-10-14 20:48:29 +0200 <geekosaur> hm
2022-10-14 20:49:09 +0200 <geekosaur> I didn't see anything obviously wrong with either Stoppable or RemoteWindows
2022-10-14 20:50:24 +0200 <T_X> sleep 3; xprop XMONAD_REMOTE [on quasselclient window] -> XMONAD_REMOTE(CARDINAL) = 0
2022-10-14 20:50:57 +0200 <T_X> maybe xmonad --restart is not enough? do I need to restart the whole X11?
2022-10-14 20:53:04 +0200 <geekosaur> you shouldn't
2022-10-14 20:53:13 +0200 <geekosaur> and that is the result you should have gotten
2022-10-14 20:53:29 +0200 <geekosaur> I wonder if something broke X.U.Timer
2022-10-14 20:54:31 +0200 <Solid> ShowWName also uses X.U.Timer and AFAIR that's still working fine, so unlikely
2022-10-14 20:56:32 +0200geekosaurwaiting for weekly backup to finish before testing locally
2022-10-14 21:05:51 +0200Guest93(~Guest93@23-123-16-69.lightspeed.cicril.sbcglobal.net)
2022-10-14 21:06:13 +0200Guest93(~Guest93@23-123-16-69.lightspeed.cicril.sbcglobal.net) (Client Quit)
2022-10-14 21:06:25 +0200Guest93(~Guest93@23-123-16-69.lightspeed.cicril.sbcglobal.net)
2022-10-14 21:09:03 +0200 <Guest93> Hi everybody.
2022-10-14 21:09:21 +0200kora9(~kora@h-98-128-228-57.NA.cust.bahnhof.se)
2022-10-14 21:10:51 +0200 <geekosaur> it's bugged
2022-10-14 21:11:03 +0200 <geekosaur> not timer, but Stoppable
2022-10-14 21:11:16 +0200chomwitt(~chomwitt@80.106.160.196)
2022-10-14 21:11:34 +0200 <geekosaur> I switched away to a different workspace, 15 seconds later the focused window in the new workspace stopped responding 😞
2022-10-14 21:11:52 +0200 <geekosaur> hi, Guest93
2022-10-14 21:12:55 +0200 <T_X> oh, well, that at least does something :D
2022-10-14 21:14:17 +0200 <Guest93> Anyone here have any problems with xmobar? For some reason, only a black bar shows up on the top. trayer seems to be working just fine though.
2022-10-14 21:15:56 +0200 <kora9> I only have problems with it when it's not configured right :)
2022-10-14 21:16:30 +0200 <kora9> Have you provided it with a config?
2022-10-14 21:17:14 +0200Guest93(~Guest93@23-123-16-69.lightspeed.cicril.sbcglobal.net) (Quit: Client closed)
2022-10-14 21:17:53 +0200jusFffffffradiofjustThumbs
2022-10-14 21:20:09 +0200justThumbsjustVain
2022-10-14 21:20:49 +0200kora9(~kora@h-98-128-228-57.NA.cust.bahnhof.se) (Quit: WeeChat 3.5)
2022-10-14 21:22:49 +0200 <geekosaur[m]> It has a built-in configuration if none is provided
2022-10-14 21:27:46 +0200 <geekosaur[m]> Hm, maybe it's not buggy, I had a terminal open so it may have stopped all of them
2022-10-14 21:28:38 +0200 <geekosaur[m]> Terminal factories are weird
2022-10-14 21:35:18 +0200 <T_X> but in theory I should see something wtih "xprop XMONAD_REMOTE" on the quasselclient window?
2022-10-14 21:35:37 +0200 <T_X> or is there another application I should test which is available on Debian (Sid)?
2022-10-14 21:36:36 +0200 <geekosaur> it'll be 0 (false) or 1 (true), should be 0 since you're unlikely to be running anything remotely
2022-10-14 21:36:50 +0200 <geekosaur> you'd have to restart X with TCP socket support enabled
2022-10-14 21:37:32 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130)
2022-10-14 21:38:32 +0200 <geekosaur> interestingly, the process I tried (sxiv, image viewer from apt install) shows state S but I know it's stopping stuff because it stopped my terminal earlier
2022-10-14 21:40:02 +0200 <T_X> geekosaur: ah, right, I tried "ssh -X someserver xmessage "foobar"; and then did a xprop XMONAD_REMOTE on it and I got a XMONAD_REMOTE(CARDINAL) = 1 indeed
2022-10-14 21:40:14 +0200 <geekosaur> no, it's accruing cpu time
2022-10-14 21:40:20 +0200 <geekosaur> so it's not opening
2022-10-14 21:40:25 +0200 <geekosaur> er, not stopping
2022-10-14 21:40:54 +0200 <geekosaur> oh wait, I tried glxgears to have something that would be active, but it's old style so probably doesn't set _NET_WM_PID
2022-10-14 21:41:25 +0200 <T_X> right, I also tried glxgears, and no, it has no _NET_WM_PID
2022-10-14 21:41:45 +0200 <geekosaur> right, just verified that
2022-10-14 21:42:06 +0200 <T_X> I also checked with "kill -s SIGSTOP" to the quasselclient pid and it indeed switches to "T". so it's not some signal handler overwrites within the client itself
2022-10-14 21:42:16 +0200 <geekosaur> (I have a bunch of debugging things in my config, I can ctrl-meta-shift-6 a window to see its props for example)
2022-10-14 21:42:58 +0200 <geekosaur> so Stoppable isn't doing its thing
2022-10-14 21:43:53 +0200 <geekosaur> the code still looks correct to me, sadly
2022-10-14 21:44:07 +0200 <geekosaur> file a bug report, maybe someone else can see something I missed
2022-10-14 21:44:24 +0200 <geekosaur> https://github.com/xmonad/xmonad-contrib/issues/new
2022-10-14 21:45:11 +0200 <T_X> ok, will do that later. thanks for looking into it though and clarifying regarding how it's supposed to work
2022-10-14 21:53:59 +0200 <geekosaur> okay, tested again with a different terminal program so I didn't lose one to check in. 15 seconds after switching workspaces, it reported suspended
2022-10-14 21:54:17 +0200noex(~null@user/noex)
2022-10-14 21:54:20 +0200 <geekosaur> "zsh: suspended (signal) xfce4-terminal"
2022-10-14 21:54:32 +0200 <geekosaur> so it *is* working here
2022-10-14 22:00:00 +0200 <geekosaur> so now I have no idea why you're having issues with it
2022-10-14 22:06:29 +0200 <geekosaur> maybe paste your whole xmonad.hs so we can check it
2022-10-14 22:06:32 +0200 <geekosaur> @where paste
2022-10-14 22:06:32 +0200 <lambdabot> Help us help you: please paste full code, input and/or output at e.g. https://paste.tomsmeding.com
2022-10-14 22:20:38 +0200Guest93(~Guest93@2602:301:77b1:450:d2b5:cb42:c9ba:35fd)
2022-10-14 22:29:25 +0200 <T_X> geekosaur: https://github.com/T-X/xmonad-config/blob/main-stoppable-test/xmonad.hs
2022-10-14 22:30:14 +0200 <T_X> ah, maybe I have an idea now. maybe I misread the example
2022-10-14 22:31:46 +0200 <T_X> ha, yes, of course, I need to switch the layout first with Alt+Space...
2022-10-14 22:32:34 +0200 <T_X> that works for quasselclient now :D. now need to check this for Firefox too, give me a second
2022-10-14 22:34:39 +0200 <geekosaur> was just about to ask if you'd alt-spaced 🙂
2022-10-14 22:35:48 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130) (Ping timeout: 264 seconds)
2022-10-14 22:43:00 +0200 <T_X> for a dedicated Firefox profile / window this does not seem to work yet though. the xprop _NET_WM_PID seems to return the PID of the initial Firefox process and it is stopped correctly, switches to T. however it's child processes which do the actual work keep on running
2022-10-14 22:43:19 +0200 <T_X> who would have thought that a shady web bitcoin mining site could turn useful for testing :D
2022-10-14 22:43:41 +0200 <geekosaur> heh
2022-10-14 22:43:52 +0200 <geekosaur> yeh, I figured it would do that
2022-10-14 22:44:18 +0200 <geekosaur> the Stoppable doc warns about chromium which works that way, but was written before firefox started doing the same
2022-10-14 22:44:29 +0200 <geekosaur> I warned you about that earlier
2022-10-14 22:44:42 +0200 <T_X> yes, I know :-)
2022-10-14 22:44:56 +0200 <geekosaur> [14 15:59:09] <geekosaur> I don't know that that layout has been tested with recent versions of firefox, since they do similar things to chromium these days and it says it doesn't work with chromium
2022-10-14 22:47:25 +0200 <T_X> maybe I need to implement something like a "killall -s SIGSTOP firefox; killall -s SIGSTOP /usr/lib/firefox/firefox" somewhere then when I switch away from my workspaces with Firefox. and somehow start a firefox with a different process names (or use another browser) for the webchat stuff then
2022-10-14 22:47:55 +0200 <T_X> the killall -s SIGSTOP /usr/lib/firefox/firefox seems to be the call which tames these workers
2022-10-14 22:48:16 +0200 <geekosaur> the real trick would be to find a programmatic way to access its taks manager so you could suspend the process corresponding to the no-longer-active window
2022-10-14 22:48:38 +0200 <geekosaur> *task
2022-10-14 22:51:06 +0200 <geekosaur> or tab as appropriate
2022-10-14 22:53:10 +0200 <T_X> yeah. though I don't quite trust the Firefox task manager. after a while Firefox seems to need more and more CPU cycles. and even stopping all active tabs via "about:performance" then usually does not lead to low CPU usage of firefox
2022-10-14 22:53:56 +0200 <T_X> hm, I'm wondering if those child processes are shared between different windows. if so would be annoying to properly stop things on a process base
2022-10-14 22:55:39 +0200 <T_X> like if you'd get the overall firefox process ID with _NET_WM_PID. but then blatantly stopping all its child processes might lead to a firefox window getting stuck which is not on a stoppable workspace
2022-10-14 22:55:44 +0200 <geekosaur> some of them correspond to active windows/tabs, others to things like the JS engine or the render backend or etc.
2022-10-14 22:56:05 +0200 <geekosaur> \so yes, stopping the wrong process would do bad things
2022-10-14 22:59:10 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130)
2022-10-14 23:16:19 +0200Guest93(~Guest93@2602:301:77b1:450:d2b5:cb42:c9ba:35fd) (Quit: Client closed)
2022-10-14 23:20:48 +0200wonko(~wjc@2a0e:1c80:2:0:45:15:19:130) (Ping timeout: 264 seconds)
2022-10-14 23:23:01 +0200 <T_X> pfff, yes, the process / window management seems confusing. found out about "about:processes" which is helpful to see which site/tab/window is using which process. initially each tab seems to get its own process. but after a few tabs for the same site then a new one is sharing the same process with another tab
2022-10-14 23:23:55 +0200 <T_X> I guess just a stoppableWithChildren is what I'd be looking for for now... and then I'd just use another Firefox profile / parent process for this one
2022-10-14 23:29:19 +0200 <geekosaur> mm, we have a process mechanism that goes the other way
2022-10-14 23:30:54 +0200 <geekosaur> X.U.Process.getPPIDChain