2023/02/10

2023-02-10 00:40:48 +0100scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 248 seconds)
2023-02-10 01:02:45 +0100scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2023-02-10 01:04:26 +0100 <ectospasm> geekosaur: I was fiddling around with my separate virtual workspace lists last night after you went to bed. I still couldn't figure out withScreen. So I gave up and tried having the same virtual workspaces on every screen. I have `sc <- countScreens`, but when I do `withScreens sc ["web", "email", "irc"]` I get a compile error, where withScreens is expecting a ScreenId not an integer. All the
2023-02-10 01:04:28 +0100 <ectospasm> examples I find either use nScreens (same way I'm trying to use it, we just call it something different), or have a literal integer following withScreens.
2023-02-10 01:09:29 +0100 <geekosaur> `countScreens` looks polymorphic to me. any chance you're using `sc` at two different types?
2023-02-10 01:12:02 +0100 <geekosaur> oh, wait, ScreenID, right. ghci> fmap (\s -> IS.withScreens (S s) ["web", "mail", "shell"]) IS.countScreens
2023-02-10 01:12:02 +0100 <geekosaur> ["0_web","0_mail","0_shell","1_web","1_mail","1_shell"]
2023-02-10 01:14:19 +0100 <geekosaur> ghci> IS.withScreen 0 ["mail", "web", "irc"] ++ IS.withScreen 1 ["shell", "code", "spare"]
2023-02-10 01:14:20 +0100 <geekosaur> ["0_mail","0_web","0_irc","1_shell","1_code","1_spare"]
2023-02-10 01:15:04 +0100 <geekosaur> note that if you're trying to use a variable instead of a constant, it won't work directly; use `fromIntegral` on the screen number, or `(S 0)`, `(S 1)`, etc.
2023-02-10 01:15:14 +0100 <geekosaur> like in the first example
2023-02-10 01:16:00 +0100 <geekosaur> (I have to admit I don't know why Spencer set ScreenIds up that way)
2023-02-10 01:32:31 +0100 <ectospasm> OK, let me give IS.withScreen another shot.
2023-02-10 01:43:33 +0100 <ectospasm> OK, got it to compile, and it works! But I see the physical workspace names in my logHook, I can fix that later.
2023-02-10 01:43:57 +0100 <ectospasm> here's my latest xmonad.hs: https://git.eldon.me/trey/XMonad/src/branch/multiheaded-fixup/xmonad.hs
2023-02-10 01:44:46 +0100 <ectospasm> My next step is to remove the gaps on monitors 1 and 2 (my two external monitors). The gap is desired for my conky output on screen 0 (primary), but kind of annoying on the other displays.
2023-02-10 01:45:34 +0100 <ectospasm> After that I'll need to sort out my logHook stuff for the multiple monitors. Ideally each screen shows its own workspaces, but that's not absolutely necessary at the moment.
2023-02-10 01:49:06 +0100 <geekosaur> there's a hook that patches up PP stuff (IS.marshallPP) and the new StatusBar module has support for workspaces shown on their own screens iirc
2023-02-10 01:50:22 +0100 <geekosaur> and if you're using Gaps to get those gaps, consider switching to spacingRaw which should give you more control
2023-02-10 01:53:29 +0100 <geekosaur> yeh, Gaps is old and very stupid. Spacing should help there. or tell conky to register as a dock and let X.H.ManageDocks deal with it
2023-02-10 01:54:45 +0100 <geekosaur> you'll want to talk to Solid about the StatusBar stuff
2023-02-10 02:10:23 +0100scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 264 seconds)
2023-02-10 02:10:28 +0100geekosaurmutters
2023-02-10 02:10:58 +0100 <geekosaur> ScreenId is a newtype over an Int with pretty much everything GNDd. What's the point?
2023-02-10 02:16:45 +0100scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2023-02-10 02:20:37 +0100werneta(~werneta@137.79.195.231) (Remote host closed the connection)
2023-02-10 02:35:24 +0100xmonadtrack(~xmonadtra@xmonad/geekosaur) (Remote host closed the connection)
2023-02-10 02:36:09 +0100geekosaur(~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2023-02-10 02:41:58 +0100geekosaur(~geekosaur@xmonad/geekosaur)
2023-02-10 02:45:40 +0100xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-02-10 02:45:40 +0100xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-02-10 02:45:40 +0100xmonadtrack(~xmonadtra@xmonad/geekosaur)
2023-02-10 03:25:19 +0100Hmmf(~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed)
2023-02-10 03:49:12 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 03:50:53 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-10 03:51:38 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 03:57:45 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-10 03:58:05 +0100 <ectospasm> OK, so I'm not running conky directly, it's conky CLI being run on various machines over SSH (plus one line locally), that pipes into dzen2 (which I believe has the --dock option, let me check)
2023-02-10 03:58:26 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 04:00:53 +0100 <ectospasm> Yeah, they're all run as `dzen2 -dock`, and absolutely positioned (because I don't know another way of doing it)
2023-02-10 04:02:52 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-10 04:03:02 +0100 <ectospasm> It's really the gaps on the other monitors that I want to fix. I'll look into spacingRaw, let me first try to understand how I set those gaps.
2023-02-10 04:03:59 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 248 seconds)
2023-02-10 04:16:48 +0100 <ectospasm> OK, so simply removing the gaps configuration is *close* to what I want. The only thing is, it only looks like my bottom dzen2 conky bar is registering as a strut (the other six on top are covered by the window on screen 0/primary)
2023-02-10 04:20:34 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-02-10 04:30:45 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 04:33:39 +0100 <ectospasm> Hmmm, I think simply reloading XMonad fixes the problem, mostly. It's like initially, the top six dzen2 bars at the bottom of my screen were covered, but relaunching XMonad (which I have mapped to winKey + xK_q) seems to fix that.
2023-02-10 04:34:23 +0100ft(~ft@p508dbcc4.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-02-10 04:34:46 +0100 <ectospasm> Now the only issue is any full screen window has the bottom cut off by these conky dzen2 docks. I can tell because the focused window border isn't show at the bottom of the window. I've even played with the focused window border to make sure.
2023-02-10 04:35:21 +0100 <ectospasm> Not a huge deal, but it means the app on that window doesn't know part of it isn't visible.
2023-02-10 04:35:29 +0100 <ectospasm> This would be a problem if this were myTerminal
2023-02-10 04:35:43 +0100 <ectospasm> And will likely be a problem when I switch back to one screen.
2023-02-10 04:40:55 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-02-10 04:41:55 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Ping timeout: 252 seconds)
2023-02-10 04:46:51 +0100mncheck(~mncheck@193.224.205.254) (Ping timeout: 265 seconds)
2023-02-10 04:59:27 +0100td_(~td@i5387090F.versanet.de) (Ping timeout: 248 seconds)
2023-02-10 05:01:02 +0100td_(~td@i53870923.versanet.de)
2023-02-10 05:23:12 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-02-10 05:28:07 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 252 seconds)
2023-02-10 08:16:35 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)
2023-02-10 08:38:07 +0100banc(banc@gateway/vpn/protonvpn/banc) (Quit: Bye, bye)
2023-02-10 08:38:27 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-02-10 08:45:15 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1) (Ping timeout: 248 seconds)
2023-02-10 08:54:56 +0100mncheck(~mncheck@193.224.205.254)
2023-02-10 09:39:32 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de) (Quit: leaving)
2023-02-10 09:47:04 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 260 seconds)
2023-02-10 10:00:07 +0100unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-02-10 10:02:46 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-02-10 10:47:54 +0100cfricke(~cfricke@user/cfricke)
2023-02-10 11:57:56 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)
2023-02-10 12:04:23 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)
2023-02-10 13:42:34 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)
2023-02-10 14:13:25 +0100mncheck(~mncheck@193.224.205.254) (Remote host closed the connection)
2023-02-10 14:13:36 +0100mncheck(~mncheck@193.224.205.254)
2023-02-10 14:42:33 +0100jabuxas(~jabuxas@user/jabuxas) (Ping timeout: 255 seconds)
2023-02-10 15:55:28 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1) (Ping timeout: 248 seconds)
2023-02-10 16:03:15 +0100cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-02-10 16:15:35 +0100ft(~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-02-10 16:34:54 +0100mc47(~mc47@xmonad/TheMC47)
2023-02-10 16:49:07 +0100Hmmf(~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722)
2023-02-10 19:33:41 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-02-10 19:49:04 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 260 seconds)
2023-02-10 20:34:35 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-02-10 20:49:19 +0100chomwitt(~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)
2023-02-10 20:50:11 +0100noze(~user@2001:41d0:a:21f1::1) (Ping timeout: 260 seconds)
2023-02-10 20:54:50 +0100noze(~user@2001:41d0:a:21f1::1)
2023-02-10 21:55:41 +0100T_X(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2023-02-10 21:55:48 +0100T_X_(~T_X@diktynna.open-mesh.org)
2023-02-10 22:38:42 +0100telser(~quassel@user/telser)
2023-02-10 23:17:35 +0100mncheck(~mncheck@193.224.205.254) (Ping timeout: 246 seconds)
2023-02-10 23:53:11 +0100jabuxas(~jabuxas@user/jabuxas)