2023/02/03

2023-02-03 02:23:43 +0100thunderrd(~thunderrd@183.182.111.134) (Ping timeout: 248 seconds)
2023-02-03 02:37:43 +0100thunderrd(~thunderrd@183.182.111.238)
2023-02-03 04:04:04 +0100banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 260 seconds)
2023-02-03 04:09:55 +0100td_(~td@i53870916.versanet.de) (Ping timeout: 252 seconds)
2023-02-03 04:11:56 +0100td_(~td@i5387090B.versanet.de)
2023-02-03 04:22:09 +0100banc(banc@gateway/vpn/protonvpn/banc)
2023-02-03 07:33:39 +0100qbt(~qbt@user/edun)
2023-02-03 07:49:00 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 255 seconds)
2023-02-03 09:24:58 +0100Solid(~slot@xmonad/slotThe) (Quit: Connection reset by pear)
2023-02-03 09:44:04 +0100ft(~ft@p4fc2a257.dip0.t-ipconnect.de) (Quit: leaving)
2023-02-03 10:00:13 +0100Ernest[m](~guydoodma@2001:470:69fc:105::2:74fe) (Quit: You have been kicked for being idle)
2023-02-03 10:09:29 +0100Solid(~slot@xmonad/slotThe)
2023-02-03 10:54:08 +0100qbt(~qbt@user/edun) (Ping timeout: 248 seconds)
2023-02-03 11:34:05 +0100malook(~Thunderbi@2a02:9b0:4000:8906:a3db:36bd:e717:5cd6)
2023-02-03 11:38:58 +0100malook(~Thunderbi@2a02:9b0:4000:8906:a3db:36bd:e717:5cd6) ()
2023-02-03 12:12:20 +0100evilop(~Urist@archlinux/op/MrElendig) (Quit: starting ww3)
2023-02-03 12:13:18 +0100MrElendig(~Urist@archlinux/op/MrElendig)
2023-02-03 12:18:14 +0100mc47(~mc47@xmonad/TheMC47)
2023-02-03 12:58:14 +0100alicecandyOM[m](~alicecand@2001:470:69fc:105::2:d7a7)
2023-02-03 13:02:57 +0100qbt(~qbt@user/edun)
2023-02-03 13:35:08 +0100iffsid(~iffsid@2001:470:69fc:105::a3e)
2023-02-03 14:16:18 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-03 14:43:32 +0100 <jabuxas> hello
2023-02-03 14:43:46 +0100unclechu(~unclechu@2001:470:69fc:105::354)
2023-02-03 14:44:36 +0100 <geekosaur> hi
2023-02-03 14:44:41 +0100 <jabuxas> i updated my xmobar to 0.46 because I was having an issue where a font was stretched for no reason, and updating to 0.46 fixed the issue for some reason
2023-02-03 14:44:43 +0100 <jabuxas> the thing is that after updating, my workspaces on xmobar are all grouped up and have no space between them
2023-02-03 14:45:01 +0100 <jabuxas> any ideas? i'll be sending both in a sec
2023-02-03 14:45:54 +0100 <jabuxas> xmobar: http://0x0.st/oCX-.hs
2023-02-03 14:45:56 +0100 <jabuxas> xmonad: http://0x0.st/oCXo.hs
2023-02-03 14:46:03 +0100 <geekosaur> not sure I can help since I don't use xmobar. might be others around who can though
2023-02-03 14:47:48 +0100 <jabuxas> this is how it looks https://0x0.st/oCXX.png
2023-02-03 14:48:54 +0100 <jabuxas> i'll be here, for now i'll be googling to see if i can find anything
2023-02-03 14:50:06 +0100 <geekosaur> xmobar.hs is kinda mangled there (no line endings)
2023-02-03 14:50:24 +0100 <geekosaur> and truncated,from the look of it
2023-02-03 14:50:57 +0100 <jabuxas> uh thats weird
2023-02-03 14:51:09 +0100 <jabuxas> i think 0x0.st f up my file
2023-02-03 14:51:14 +0100 <jabuxas> let me try again to send it
2023-02-03 14:52:24 +0100 <jabuxas> xmobar: https://bpa.st/4JY7I
2023-02-03 14:52:28 +0100 <jabuxas> now it's right
2023-02-03 15:05:55 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca) (Remote host closed the connection)
2023-02-03 15:06:36 +0100rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-05-174-88-194-86.dsl.bell.ca)
2023-02-03 15:22:55 +0100 <jabuxas> i guess it is a problem with my ppWsSep, commenting it out and now its back to normal
2023-02-03 15:23:15 +0100 <jabuxas> i just dont know why it would break after an update
2023-02-03 15:27:06 +0100 <geekosaur> font rendering issue? more specifically not handling spaces correctly
2023-02-03 15:34:43 +0100 <jabuxas> maybe
2023-02-03 16:17:13 +0100ft(~ft@p4fc2a257.dip0.t-ipconnect.de)
2023-02-03 16:36:52 +0100matijja(~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in)
2023-02-03 16:40:45 +0100matijja(~matijja@193.77.181.201)
2023-02-03 17:29:15 +0100qbt(~qbt@user/edun) (Ping timeout: 252 seconds)
2023-02-03 17:41:24 +0100 <liskin> jabuxas: can you try using a bog standard font like "sans-serif"? if spaces are still missing then I'd try fiddling with your wrapSep in xmonad.hs
2023-02-03 17:41:55 +0100 <liskin> it could be an xmobar/pango bug though, that wrapSep looks like it should at least render the spaceā€¦
2023-02-03 18:09:52 +0100werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-02-03 18:33:35 +0100 <jabuxas> i'll give it a try
2023-02-03 18:34:27 +0100jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-02-03 18:42:31 +0100 <jabuxas> seems to be a bug with xmobarColor when used on ppWsSep
2023-02-03 18:43:11 +0100 <jabuxas> removing it completely fixes it, using another function like xmobarBorder works normally
2023-02-03 18:44:28 +0100 <jabuxas> it doesnt matter if using sans-serif or cartograph cf
2023-02-03 18:46:03 +0100 <geekosaur> I noticed stuff like #rrggbb:7 in your spec, if they added to the color spec I wonder if they're doing something silly like eating trailing spaces
2023-02-03 18:46:31 +0100 <geekosaur> although those should be wrapped inside <fc>, shouldn't they?
2023-02-03 18:53:36 +0100 <jabuxas> i can try removing it, i dont think they did much or i didnt notice it myself at least
2023-02-03 18:54:28 +0100 <jabuxas> doenst seem to be the case
2023-02-03 18:55:12 +0100 <geekosaur> I don't mean you should do so, I mean they translate to that
2023-02-03 18:55:23 +0100 <geekosaur> look at what `xmobarColor` produces
2023-02-03 18:56:18 +0100 <geekosaur> in any case this sounds like an xmobar bug
2023-02-03 20:24:40 +0100mvk(~mvk@2607:fea8:5caa:ac00::f944)
2023-02-03 22:18:56 +0100mvk(~mvk@2607:fea8:5caa:ac00::f944) (Ping timeout: 248 seconds)
2023-02-03 22:34:52 +0100Natch(~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se) (Remote host closed the connection)
2023-02-03 22:41:06 +0100Natch(~natch@c-9e07225c.038-60-73746f7.bbcust.telenor.se)
2023-02-03 23:57:31 +0100mvk(~mvk@2607:fea8:5caa:ac00::f944)