2025/09/19

Newest at the top

2025-09-19 04:36:21 +0200haskellbridge(~hackager@syn-096-028-224-214.res.spectrum.com) hackager
2025-09-19 04:35:52 +0200haskellbridge(~hackager@syn-096-028-224-214.res.spectrum.com) (Remote host closed the connection)
2025-09-19 04:19:01 +0200 <haskellbridge> <iqubic (she/her)> That's the broken version.
2025-09-19 04:18:57 +0200 <haskellbridge> <iqubic (she/her)> https://dpaste.org/0pATb/raw
2025-09-19 04:18:34 +0200 <haskellbridge> <iqubic (she/her)> geekosaur: Here's what I get for not using a tool with proper syntax highlighting... The error was that I was missing a few commas on the line "-l" and "-h".
2025-09-19 03:55:25 +0200 <haskellbridge> <iqubic (she/her)> Why is there no easy way to search through a repo that's being hosted on codeberg?
2025-09-19 03:23:25 +0200 <haskellbridge> <iqubic (she/her)> Alright... I've removed the Battery section for now and it seems to work...
2025-09-19 02:59:41 +0200 <haskellbridge> <iqubic (she/her)> Sounds good.
2025-09-19 02:59:11 +0200 <geekosaur> I'm not seeing anything here, you probably need someone who knows xmobar better
2025-09-19 02:54:06 +0200 <haskellbridge> <iqubic (she/her)> It should...
2025-09-19 02:53:09 +0200 <geekosaur> \I was trying to figure out if your xmobar actually supported the "trick" in that blog page
2025-09-19 02:53:03 +0200 <haskellbridge> <iqubic (she/her)> But if the fancy -w 0 trick was added in 0.36, then it should just work, right?
2025-09-19 02:52:44 +0200 <geekosaur> xmonad isn't actually relevant here
2025-09-19 02:52:38 +0200 <geekosaur> right, my asking about that was a mistake, I meant xmobar
2025-09-19 02:52:06 +0200 <haskellbridge> <iqubic (she/her)> I'm pulling the latest versions of XMonad and XMonad-Contrib. I'm not pulling the latest version of XMobar.
2025-09-19 02:51:46 +0200 <geekosaur> https://hackage.haskell.org/package/xmobar-0.50
2025-09-19 02:51:07 +0200 <geekosaur> then it's not getting the latest
2025-09-19 02:48:41 +0200 <haskellbridge> <iqubic (she/her)> That's what "xmobar --version" gives me.
2025-09-19 02:48:22 +0200 <haskellbridge> <iqubic (she/her)> I'm using xmobar 0.49
2025-09-19 02:48:02 +0200 <haskellbridge> <iqubic (she/her)> I'm using Nix and I'm telling Nix to download the XMonad and XMonad-Contrib libraries from hackage and using that to compile my XMonad config.
2025-09-19 02:47:46 +0200 <geekosaur> 0.50 in fact
2025-09-19 02:47:23 +0200 <geekosaur> right, I just checked versions, the trick came with 0.36 but they're on at least 0.45 now
2025-09-19 02:46:23 +0200 <haskellbridge> <iqubic (she/her)> I don't think so. I'm using the latest version from Hackage.
2025-09-19 02:45:10 +0200 <geekosaur> er, xmobar build
2025-09-19 02:45:02 +0200 <geekosaur> are you using an xmonad build from git?
2025-09-19 02:44:50 +0200 <geekosaur> hm
2025-09-19 02:44:42 +0200 <haskellbridge> <iqubic (she/her)> Yeah, BatteryN is basically the same but just lets you provide a string to be used as the alias in the template string.
2025-09-19 02:43:07 +0200 <haskellbridge> <iqubic (she/her)> Is there a way I can write my config in actual haskell and call it directly from my XMonad config? I assume GHC compiler errors would be better than the errors from the XMobar parser.
2025-09-19 02:42:56 +0200 <geekosaur> hm, maybe not. your page uses BatteryN, you're using BatteryP
2025-09-19 02:41:07 +0200 <geekosaur> oh. I see a problem
2025-09-19 02:40:27 +0200 <haskellbridge> <iqubic (she/her)> I see...
2025-09-19 02:40:13 +0200 <geekosaur> this is one of the reasons I don't run xmobar, debugging config errors is a nightmare
2025-09-19 02:40:07 +0200 <haskellbridge> <iqubic (she/her)> Same error
2025-09-19 02:39:49 +0200 <haskellbridge> <iqubic (she/her)> Right... Removing the line that's supposed to be a comment still doesn't work.
2025-09-19 02:39:09 +0200 <geekosaur> that part shouldn't affect it (I think)
2025-09-19 02:38:31 +0200 <haskellbridge> <iqubic (she/her)> The battery config was taken from here: https://jao.io/blog/xmobar-a-battery-trick.html and lightly modified it.
2025-09-19 02:37:47 +0200 <geekosaur> xmobar's config parser is really horrible
2025-09-19 02:37:30 +0200 <geekosaur> the other ones look fine, I think they're all builtins. so yeh, I think I'd try removing the "comment"
2025-09-19 02:36:46 +0200 <geekosaur> it might be
2025-09-19 02:36:37 +0200 <haskellbridge> <iqubic (she/her)> Is the issue that I'm commenting out the ALSA section because I haven't finished configuring it?
2025-09-19 02:36:34 +0200 <geekosaur> also I don't think comments work in there. It only looks like Haskell
2025-09-19 02:35:35 +0200 <geekosaur> so it fails to parse "sepChar" with a weird error when the real problem is in the "Run" list
2025-09-19 02:35:31 +0200 <haskellbridge> <iqubic (she/her)> I'm just trying to run my XMobar config...
2025-09-19 02:35:17 +0200 <haskellbridge> <iqubic (she/her)> Hmm.... How do I figure it out?
2025-09-19 02:33:31 +0200 <geekosaur> that's usually a missing pugin combined with a horrible parser
2025-09-19 02:31:35 +0200 <haskellbridge> <iqubic (she/her)> geekosaur: Do you know what's going wrong here?
2025-09-19 02:20:14 +0200 <haskellbridge> <iqubic (she/her)> expecting space or "Run"
2025-09-19 02:20:13 +0200 <haskellbridge> <iqubic (she/her)> unexpected "s"
2025-09-19 02:20:08 +0200 <haskellbridge> <iqubic (she/her)> When I try to run xmobar from the terminal I'm getting an error: Invalid configuration file: "Config" (line 34, column 10):
2025-09-19 02:19:02 +0200 <haskellbridge> <iqubic (she/her)> And it's not working properly...