Newest at the top
2025-09-18 08:26:31 +0200 | wz1000- | (~wz1000@static.194.167.62.46.clients.your-server.de) (Ping timeout: 256 seconds) |
2025-09-18 08:25:57 +0200 | <haskellbridge> | <iqubic (she/her)> So, I've read the quick-start guide for xmobar, but I don't know what all the modules are. Is there a list of commands I can have it run? |
2025-09-18 08:25:45 +0200 | wz1000_ | (~wz1000@2a01:4f9:c012:de50::1) |
2025-09-18 07:38:00 +0200 | OftenFaded | (~Al@user/tisktisk) OftenFaded |
2025-09-18 07:31:01 +0200 | OftenFaded | (~Al@user/tisktisk) (Ping timeout: 265 seconds) |
2025-09-18 06:58:29 +0200 | <haskellbridge> | <dpn> it's using X resources syntax - so however that works most likely |
2025-09-18 06:54:50 +0200 | <haskellbridge> | <iqubic (she/her)> Does XMobar support fallback fonts or not? |
2025-09-18 06:41:45 +0200 | <haskellbridge> | ... long message truncated: https://kf8nh.com/_heisenbridge/media/kf8nh.com/nBfhHyaFSysrvoERtAgzTfoB/jiKHn8SsqVA (24 lines) |
2025-09-18 06:41:45 +0200 | <haskellbridge> | <dpn> looking at my old config, it looks like i used a nerd font then: |
2025-09-18 06:22:04 +0200 | <geekosaur> | no idea |
2025-09-18 06:17:49 +0200 | <haskellbridge> | <iqubic (she/her)> Does XMobar support Nerdfonts? |
2025-09-18 06:12:33 +0200 | <geekosaur> | lots, including on its website (https://codeberg.org/xmobar/xmobar/src/branch/master/doc/quick-start.org) |
2025-09-18 06:10:46 +0200 | <haskellbridge> | <iqubic (she/her)> Are there any guides on how to set up XMobar? |
2025-09-18 06:09:05 +0200 | <haskellbridge> | <iqubic (she/her)> I think so, yeah. I'm not really using any of the advanced Polybar features. |
2025-09-18 06:08:19 +0200 | <geekosaur> | it would certainly be easier to set up, but does it do what you want? |
2025-09-18 06:06:53 +0200 | <haskellbridge> | <iqubic (she/her)> Should I switch from Polybar to XMobar? XMobar seems like it might work better for me, seeing as it was specifically made for XMonad. |
2025-09-18 06:04:58 +0200 | <geekosaur> | *mining *thought |
2025-09-18 06:04:29 +0200 | <geekosaur> | and even less happy with their data minimg. I thouyght google's was bad, firefox managed to outdo them |
2025-09-18 06:03:58 +0200 | <geekosaur> | I'm really not happy with firefox development over the past couple years |
2025-09-18 06:03:08 +0200 | <geekosaur> | because of things like that and a UI that seemed to be getting worse all the time |
2025-09-18 06:03:00 +0200 | <haskellbridge> | <iqubic (she/her)> Oh, nice. |
2025-09-18 06:02:50 +0200 | <haskellbridge> | <iqubic (she/her)> Why? |
2025-09-18 06:02:48 +0200 | <geekosaur> | yes, it kills the running bars and runs the new ones as specified by your function |
2025-09-18 06:02:16 +0200 | <geekosaur> | but I gave up on ff long ago |
2025-09-18 06:02:15 +0200 | <haskellbridge> | <iqubic (she/her)> geekosaur: Does that work with hot-plugging monitors while the system is running? |
2025-09-18 06:01:56 +0200 | <geekosaur> | chrome likes it fine. nop idea what ff is doing |
2025-09-18 06:01:13 +0200 | <geekosaur> | the function you pass to dyanmicSBs is run once per screen, with the screen number as parameter. you do fir each screen what you would do with withSB, but you're in X so you can query stuff yourself or whatever (which is why there's a `pure` wrapped around it in the example) |
2025-09-18 06:01:13 +0200 | <haskellbridge> | <dpn> https://kf8nh.com/_heisenbridge/media/matrix.org/ZRNnakKRrsXhuXSAundwtahg/Z_CZ-LDEdnA/image.png |
2025-09-18 06:01:07 +0200 | <haskellbridge> | <iqubic (she/her)> Firefox doesn't like that website |
2025-09-18 06:00:58 +0200 | <haskellbridge> | <iqubic (she/her)> Error code: SSL_ERROR_RX_RECORD_TOO_LONG |
2025-09-18 06:00:50 +0200 | <haskellbridge> | <iqubic (she/her)> Secure connection failed |
2025-09-18 05:59:05 +0200 | <geekosaur> | https://0x0.st/KTsa.png fwiw |
2025-09-18 05:58:08 +0200 | <haskellbridge> | <iqubic (she/her)> I'm not understanding how that works... |
2025-09-18 05:56:19 +0200 | <geekosaur> | https://hackage.haskell.org/package/xmonad-contrib-0.18.1/docs/XMonad-Hooks-StatusBar.html#g:4 |
2025-09-18 05:53:37 +0200 | <haskellbridge> | <iqubic (she/her)> Right, but the question I actually have is "how do I get a new polybar instance spawned when I plug in a new monitor and killed when the monitor is unplugged"? |
2025-09-18 05:53:15 +0200 | <haskellbridge> | <dpn> iirc dzen works like this too - i couldn't quite get it playing nicely with lightdm |
2025-09-18 05:52:46 +0200 | <geekosaur> | if you followed what I said above, I have 3 |
2025-09-18 05:52:37 +0200 | <geekosaur> | yes |
2025-09-18 05:52:32 +0200 | <haskellbridge> | <iqubic (she/her)> Yeah, but does that work with multiple monitors? |
2025-09-18 05:52:17 +0200 | <geekosaur> | I use dbus to feed xmonad-log-applet built for mate-panel |
2025-09-18 05:51:54 +0200 | <geekosaur> | okay, looks like it's not specifically an xmonad plugin, it's a dbus plugin. you then configure your xmonad.hs to send xmonad PP information over dbus (see for example https://github.com/geekosaur/xmonad.hs/blob/hilfy-2023/xmonad.hs#L426-L444) |
2025-09-18 05:51:38 +0200 | <haskellbridge> | <iqubic (she/her)> geekosaur: Do you use any bars? |
2025-09-18 05:50:55 +0200 | <haskellbridge> | <dpn> i should check out poly |
2025-09-18 05:50:42 +0200 | <haskellbridge> | <dpn> i still haven't added a bar - running stalonetray and nothing else ... taffy was nice but used too much memory |
2025-09-18 05:49:39 +0200 | <haskellbridge> | <iqubic (she/her)> I haven't found any Polybar and XMonad plugin. |
2025-09-18 05:49:39 +0200 | <geekosaur> | I use two editor panes on mine 🙂 |
2025-09-18 05:49:23 +0200 | <haskellbridge> | <iqubic (she/her)> Oh? Does it? |
2025-09-18 05:49:14 +0200 | <geekosaur> | but I think polybar has a plugin that will let you get information directly from xmonad |
2025-09-18 05:49:07 +0200 | <haskellbridge> | <dpn> geekosaur: i recently bought an extra wide monitor - now i have ws 1 and 2 on the same monitor basically (1 = code, 2 = browser) |
2025-09-18 05:48:51 +0200 | <geekosaur> | I don't know how polybar will work there given EWMH and xmonad differ on how workspaces relate to monitors |