Home liberachat/#xmonad: Logs Calendar

Logs: liberachat/#xmonad

←Prev  Next→ 184,980 events total
2023-02-09 17:14:06 <geekosaur> dzen2 has its own problem. sometimes you need a parameter for it to set struts, and you have to make sure it's positioned exactly on the screen border or it won't set one anyway
2023-02-09 17:14:15 <geekosaur> off by one pixel -> it ignores you
2023-02-09 17:14:24 <Hmmf> Ha
2023-02-09 17:14:26 <Hmmf> I see
2023-02-09 17:14:51 <geekosaur> anyway I would remove all your existing uses of `avoidStruts` and put one on line 229
2023-02-09 17:15:06 <Hmmf> Yes that makes a lot of sense.
2023-02-09 17:15:15 <Hmmf> What are you guys using usually? xmobar?
2023-02-09 17:15:27 <geekosaur> many use xmobar, some use polybar
2023-02-09 17:15:37 <geekosaur> I use xmonad with MATE so I have a couple of mate-panels
2023-02-09 17:17:41 <Hmmf> Yes I remember why I did it that way, I wanted some workspace with avoidStruts and some without. I guess there is no good solution for that atm.
2023-02-09 17:18:21 <geekosaur> https://github.com/geekosaur/xmonad.hs/blob/skkukuk/xmonad.hs#L139-L153
2023-02-09 17:18:54 <geekosaur> `avoidStrutsOn []` means struts default off but can be toggled on
2023-02-09 17:20:00 <Hmmf> Ah I see. Explicitely removing the avoidance on the appropriate workspaces but leaving it on globally.
2023-02-09 17:23:36 × Hmmf quits (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed)
2023-02-09 17:26:31 Hmmf joins (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722)
2023-02-09 17:29:22 <Hmmf> Yes I'm getting somewhere. So now strut avoidance is perfect. It's just a matter of having dzen2 drawn behind the windows.
2023-02-09 17:29:47 <Hmmf> Like, if I toggleStruts, windows resize like they should, it's just that dzen2 is over them.
2023-02-09 17:33:47 <geekosaur> there may be an option for that. normally something operating in dock mode lowers itself. (docks are self-managing, we're not supposed to touch them)
2023-02-09 17:34:59 × chomwitt quits (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)
2023-02-09 17:35:52 <Hmmf> It's not that I am an expert on the matter but I have a feeling that dzen2 doesn't really comply with whatever standard they should take care of.
2023-02-09 17:36:04 <Hmmf> Oh well, at least my xmonad is doing its part now.
2023-02-09 17:38:12 <geekosaur> nope, it's very minimal and doesn't do EWMH properly
2023-02-09 17:38:30 <geekosaur> partially because it normally wants to be a normal window, not a dock
2023-02-09 17:39:19 <Hmmf> heh. Ok time to switch then I guess.
2023-02-09 17:41:36 × cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-02-09 17:44:24 werneta joins (~werneta@137.79.195.231)
2023-02-09 17:47:52 × Hmmf quits (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed)
2023-02-09 17:53:01 Hmmf joins (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722)
2023-02-09 18:00:01 cfricke joins (~cfricke@user/cfricke)
2023-02-09 18:11:00 × cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-02-09 18:35:00 cfricke joins (~cfricke@user/cfricke)
2023-02-09 18:42:44 × Hmmf quits (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed)
2023-02-09 18:42:55 Hmmf joins (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722)
2023-02-09 18:45:31 × cfricke quits (~cfricke@user/cfricke) (Ping timeout: 248 seconds)
2023-02-09 19:11:02 ft joins (~ft@p508dbcc4.dip0.t-ipconnect.de)
2023-02-09 19:15:36 × Hmmf quits (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed)
2023-02-09 19:17:00 chomwitt joins (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1)
2023-02-09 19:17:29 cfricke joins (~cfricke@user/cfricke)
2023-02-09 20:04:10 × cfricke quits (~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-02-09 21:04:29 Hmmf joins (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722)
2023-02-09 21:28:17 × malook quits (~Thunderbi@2a02:9b0:4000:8906:fa4b:47f4:65e4:a888) (Remote host closed the connection)
2023-02-09 22:08:35 × chomwitt quits (~chomwitt@2a02:587:7a12:aa00:1ac0:4dff:fedb:a3f1) (Ping timeout: 264 seconds)
2023-02-09 22:12:06 × mc47 quits (~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-02-09 23:40:48 × scardinal quits (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 248 seconds)
2023-02-10 00:02:45 scardinal joins (~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2023-02-10 00:04:26 <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 00:04:28 <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 00:09:29 <geekosaur> `countScreens` looks polymorphic to me. any chance you're using `sc` at two different types?
2023-02-10 00:12:02 <geekosaur> oh, wait, ScreenID, right. ghci> fmap (\s -> IS.withScreens (S s) ["web", "mail", "shell"]) IS.countScreens
2023-02-10 00:12:02 <geekosaur> ["0_web","0_mail","0_shell","1_web","1_mail","1_shell"]
2023-02-10 00:14:19 <geekosaur> ghci> IS.withScreen 0 ["mail", "web", "irc"] ++ IS.withScreen 1 ["shell", "code", "spare"]
2023-02-10 00:14:20 <geekosaur> ["0_mail","0_web","0_irc","1_shell","1_code","1_spare"]
2023-02-10 00:15:04 <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 00:15:14 <geekosaur> like in the first example
2023-02-10 00:16:00 <geekosaur> (I have to admit I don't know why Spencer set ScreenIds up that way)
2023-02-10 00:32:31 <ectospasm> OK, let me give IS.withScreen another shot.
2023-02-10 00:43:33 <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 00:43:57 <ectospasm> here's my latest xmonad.hs: https://git.eldon.me/trey/XMonad/src/branch/multiheaded-fixup/xmonad.hs
2023-02-10 00:44:46 <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 00:45:34 <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 00:49:06 <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 00:50:22 <geekosaur> and if you're using Gaps to get those gaps, consider switching to spacingRaw which should give you more control
2023-02-10 00:53:29 <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 00:54:45 <geekosaur> you'll want to talk to Solid about the StatusBar stuff
2023-02-10 01:10:23 × scardinal quits (~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 264 seconds)
2023-02-10 01:10:28 geekosaur mutters
2023-02-10 01:10:58 <geekosaur> ScreenId is a newtype over an Int with pretty much everything GNDd. What's the point?
2023-02-10 01:16:45 scardinal joins (~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2023-02-10 01:20:37 × werneta quits (~werneta@137.79.195.231) (Remote host closed the connection)
2023-02-10 01:35:24 × xmonadtrack quits (~xmonadtra@xmonad/geekosaur) (Remote host closed the connection)
2023-02-10 01:36:09 × geekosaur quits (~geekosaur@xmonad/geekosaur) (Quit: Leaving)
2023-02-10 01:41:58 geekosaur joins (~geekosaur@xmonad/geekosaur)
2023-02-10 01:45:40 xmonadtrack joins (~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-02-10 01:45:40 × xmonadtrack quits (~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-02-10 01:45:40 xmonadtrack joins (~xmonadtra@xmonad/geekosaur)
2023-02-10 02:25:19 × Hmmf quits (~Hmmf@2a01:e0a:582:bb40:e5c6:f484:7015:1722) (Quit: Client closed)
2023-02-10 02:49:12 rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 02:50:53 × rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-10 02:51:38 rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 02:57:45 × rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-10 02:58:05 <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 02:58:26 rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 03:00:53 <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 03:02:52 × rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-10 03:03:02 <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 03:03:59 × banc quits (banc@gateway/vpn/protonvpn/banc) (Ping timeout: 248 seconds)
2023-02-10 03:16:48 <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 03:20:34 banc joins (banc@gateway/vpn/protonvpn/banc)
2023-02-10 03:30:45 rekahsoft joins (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-10 03:33:39 <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 03:34:23 × ft quits (~ft@p508dbcc4.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-02-10 03:34:46 <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 03:35:21 <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 03:35:29 <ectospasm> This would be a problem if this were myTerminal
2023-02-10 03:35:43 <ectospasm> And will likely be a problem when I switch back to one screen.
2023-02-10 03:40:55 ft joins (~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-02-10 03:41:55 × rekahsoft quits (~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Ping timeout: 252 seconds)
2023-02-10 03:46:51 × mncheck quits (~mncheck@193.224.205.254) (Ping timeout: 265 seconds)
2023-02-10 03:59:27 × td_ quits (~td@i5387090F.versanet.de) (Ping timeout: 248 seconds)
2023-02-10 04:01:02 td_ joins (~td@i53870923.versanet.de)

All times are in UTC.