2021/05/28

2021-05-28 00:10:04 +0200seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-05-28 00:27:47 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Remote host closed the connection)
2021-05-28 00:29:42 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 00:57:37 +0200allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 01:00:47 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 252 seconds)
2021-05-28 01:12:16 +0200allbery_bgeekosaur
2021-05-28 01:42:01 +0200tremon_(~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
2021-05-28 02:07:55 +0200sszark(~sszark@h-85-24-213-180.A392.priv.bahnhof.se) (Ping timeout: 252 seconds)
2021-05-28 02:32:49 +0200jg(~jg@47.149.222.98)
2021-05-28 02:42:55 +0200 <jg> Hi everyone, I am going honesty mad, I am running a barebones install of arch on virtualbox, I used static-stack from the aur to compile everyting which includes: xmonad, xmobar, and xmonad-contrib, I added all flags to xmobar except for alsa. I am currently getting the error .xmobarrc: hGetContents: invalid argument (invalid byte sequence) when
2021-05-28 02:42:55 +0200 <jg> trying to launch xmobar. When I remove the degrees symbol the xmobar launches and compiles just fine. Running 'file .xmobarrc' confirms it is a UTF-8 file. and when I run localectl list-locales it returns en_US.UTF-8. How can I work around and get the degree's symbol to compile?
2021-05-28 02:45:46 +0200 <geekosaur> you might make sure the locale xmonad and xmobar run from is the same as the one in the terminal; most distributions that aren't Debian-based separate them. does xmobar run correctly from a terminal?
2021-05-28 02:46:48 +0200 <jg> @ge
2021-05-28 02:46:48 +0200 <lambdabot> Maybe you meant: get-shapr get-topic wn v rc pl let id ghc do bf @ ? .
2021-05-28 02:46:59 +0200 <jg> geekosaur this is when trying to run from terminal directly
2021-05-28 02:47:29 +0200 <jg> I havent tried to run from xmonad yet
2021-05-28 02:48:48 +0200allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 02:51:10 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 264 seconds)
2021-05-28 02:51:29 +0200allbery_bgeekosaur
2021-05-28 02:53:05 +0200 <geekosaur> hm. I suggest posting this on xmobar's issue tracker (https://github.com/jaor/xmobar/issues) since nobody here has been able to help
2021-05-28 02:53:44 +0200 <jg> alright I will thanks
2021-05-28 02:53:53 +0200 <geekosaur> possibly there is a bug, although utf8 support is supposed to be in xmobar at least with a flag but that doesn't control the .xmobarrc
2021-05-28 02:54:14 +0200 <geekosaur> also sorry my network chose that time to drop
2021-05-28 02:54:47 +0200 <jg> it is no worries! I just feel like it is probably something so small since no one else has had the issue lol
2021-05-28 03:06:11 +0200 <jg> I submitted something geekosaur thank you, I hope I put enough info but I can always add more if needed
2021-05-28 03:14:18 +0200 <burp> and this time without the degree symbol it works?
2021-05-28 03:23:25 +0200 <jg> yes sir burp
2021-05-28 03:23:56 +0200themainman(~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-05-28 03:26:46 +0200 <burp> well then
2021-05-28 03:27:52 +0200 <jg> i tried jaor's suggestion of doing \x0b, however it shows a box so im not sure lol the font is installed
2021-05-28 03:38:59 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Quit: Leaving)
2021-05-28 03:40:09 +0200 <burp> try \x2103
2021-05-28 03:40:17 +0200leeb(~leeb@2001:268:c04f:ba65:425b:d8ff:fe03:4cd)
2021-05-28 03:41:06 +0200 <jg> \xb0 works per jaor, i wonder why the normal doesnt work
2021-05-28 03:42:30 +0200 <jg> burp, that also works and includes the C, what font is that part of?
2021-05-28 03:42:41 +0200 <burp> the font you choose
2021-05-28 03:42:48 +0200 <burp> it's just another unicode symbol
2021-05-28 03:42:55 +0200 <burp> just looked it up on wikipedia https://en.wikipedia.org/wiki/Degree_symbol
2021-05-28 03:43:03 +0200 <burp> see the right side: U+2103
2021-05-28 03:43:19 +0200 <burp> and above that U+B0
2021-05-28 03:43:30 +0200 <burp> which is your \xb0
2021-05-28 03:44:21 +0200 <jg> well its a great work around :) lmao I feel stupid af
2021-05-28 03:45:15 +0200 <burp>
2021-05-28 03:46:57 +0200 <jg> hmm well maybe I will swap over my main machine to stack and get off of arches repos...
2021-05-28 03:51:56 +0200jg(~jg@47.149.222.98) (Quit: Client closed)
2021-05-28 03:54:39 +0200jg(~jg@47.149.222.98)
2021-05-28 03:54:53 +0200 <jg> omg the fullscreen handling on this version is so much better than my toggle work around on .15
2021-05-28 03:55:19 +0200 <jg> now to make the workspace clickable lol
2021-05-28 04:34:29 +0200benin7(~benin@183.82.177.19)
2021-05-28 04:34:48 +0200benin(~benin@183.82.176.197) (Ping timeout: 265 seconds)
2021-05-28 04:34:48 +0200benin7benin
2021-05-28 04:35:17 +0200td_(~td@94.134.91.249) (Ping timeout: 252 seconds)
2021-05-28 04:37:11 +0200td_(~td@muedsl-82-207-238-082.citykom.de)
2021-05-28 04:45:09 +0200berberman(~berberman@user/berberman)
2021-05-28 04:46:30 +0200berberman_(~berberman@user/berberman) (Ping timeout: 264 seconds)
2021-05-28 06:08:20 +0200 <jg> quick question when using the StatusBar Hook for anyone that better understand this than me, I have mine set up like the tutorial shown, to use 'withEasySB (statusBarProp "xmobar" (pure myXmobarPP)) defToggleStrutsKey' which works great until I recompile/restart xmonad. After restarting xmonad, the xmobar is stuck on the screen and does not allow
2021-05-28 06:08:20 +0200 <jg> for the toggling of struts. If I open a new program or window however, it goes back to behaving and toggling struts. I am not sure if this is on my end or maybe a bug somewhere
2021-05-28 06:13:00 +0200qbt(~edun@user/edun)
2021-05-28 06:36:31 +0200incertia(~incertia@d4-50-26-103.nap.wideopenwest.com)
2021-05-28 06:44:47 +0200 <xacktm> jg, you've used teh `docks` wrapper to apply dock bar support? previous method of modifying just one hook is insufficient since a few years ago; `docks` does more than one
2021-05-28 06:44:59 +0200 <xacktm> does more than one hook*
2021-05-28 06:46:51 +0200 <jg> I'll upload a paste bin, im not 100 % sure
2021-05-28 06:49:52 +0200 <jg> https://pastebin.com/3ax6cECV
2021-05-28 06:50:26 +0200 <jg> xacktm this is how I am currently doing it, I've just pieced this together sadly as I am learning
2021-05-28 06:52:19 +0200 <xacktm> cargo culting woo! That's how I did it back in the day too :p
2021-05-28 06:53:10 +0200 <xacktm> and yeah I don't see the docks function in there, here's the page, docs should be good but lmk if you get stuck: https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Hooks-ManageDocks.html
2021-05-28 06:53:46 +0200 <jg> I'll give it a go thank you, Yea I am tinkering with the new .16 and .17 lol
2021-05-28 06:54:19 +0200 <jg> the new statusBar has some cool stuff in it
2021-05-28 07:04:41 +0200 <jg> xacktm I'm having no luck lol
2021-05-28 07:04:54 +0200 <xacktm> new paste?
2021-05-28 07:06:43 +0200 <jg> https://pastebin.com/eKenqVmd I appreciate the help by the way xacktm
2021-05-28 07:06:56 +0200 <jg> wait
2021-05-28 07:06:59 +0200 <jg> wrong paste bin
2021-05-28 07:08:37 +0200 <xacktm> ok lol, was gonna say..
2021-05-28 07:08:42 +0200 <jg> xacktm - here is my changes https://pastebin.com/ZSz1YhiP
2021-05-28 07:09:05 +0200 <jg> the status bar has the toggle struts to mod b in the git xmonad-contribs
2021-05-28 07:11:05 +0200 <jg> it does not compile if i add docks def to my main below ewmh
2021-05-28 07:12:45 +0200 <xacktm> ah, well you've already used `def` in myXMobarPP; as long as you apply it somwhere in that . function chain
2021-05-28 07:13:02 +0200 <xacktm> try right below ewmh, ". docks"
2021-05-28 07:13:24 +0200 <xacktm> which should insert docks in the composition chain after the xmobar config
2021-05-28 07:13:59 +0200 <xacktm> :t (.)
2021-05-28 07:14:00 +0200 <lambdabot> (b -> c) -> (a -> b) -> a -> c
2021-05-28 07:14:10 +0200 <xacktm> :t ($)
2021-05-28 07:14:11 +0200 <lambdabot> (a -> b) -> a -> b
2021-05-28 07:14:39 +0200 <jg> xacktm with it above xmobar chain it still doesnt behave after the recompile until I open and close a terminal
2021-05-28 07:14:40 +0200 <xacktm> I still don't have a good intuition of (.) and sometimes just convert them to function application $
2021-05-28 07:14:55 +0200 <jg> I can try changing them all to $
2021-05-28 07:15:09 +0200 <xacktm> shouldn't matter, it compiles though?
2021-05-28 07:15:24 +0200 <jg> yea it compiles the bar just doesnt want to get off the screen lmao
2021-05-28 07:15:56 +0200 <jg> its bizzare that opening a terminal causes it to then allow for toggling of struts
2021-05-28 07:17:56 +0200 <xacktm> weird, not to sound cliche` but have you tried a complete X restart?
2021-05-28 07:18:43 +0200 <jg> yes haha, restart was the first thing I tried
2021-05-28 07:18:54 +0200 <jg> I just did it again to check my sanity lol
2021-05-28 07:19:06 +0200 <jg> if you run the config does it work or cause those same issues?
2021-05-28 07:20:21 +0200 <xacktm> it would be good for someone to reproduce but I've got my windows tied up atm :S
2021-05-28 07:20:33 +0200 <xacktm> and I'm on 0.15 still
2021-05-28 07:21:04 +0200 <jg> damn yea my main rig is on .15, im messing with this in a vm
2021-05-28 07:22:31 +0200 <xacktm> oh, check the docks, the layout needs the avoidStruts modifier
2021-05-28 07:22:39 +0200 <xacktm> check the docs*
2021-05-28 07:24:22 +0200 <jg> yea I added the avoidStruts modifier
2021-05-28 07:24:28 +0200 <jg> no cigar
2021-05-28 07:24:54 +0200 <xacktm> :/ new paste?
2021-05-28 07:25:24 +0200 <jg> it was the same as the old paste i recently sent, i added avoidStruts around (tiled ||| Mirror ... etc)
2021-05-28 07:25:55 +0200 <jg> like of a fresh boot its chill, its only after an xmonad --restart
2021-05-28 07:25:55 +0200 <xacktm> kk, and you did the same restart X song and dance I'm guessing :S
2021-05-28 07:25:57 +0200 <jg> that it fails
2021-05-28 07:26:42 +0200 <jg> which makes it so bizarre because doesnt doing exec xmonad cause a recompile and restart
2021-05-28 07:28:48 +0200 <jg> opening any window causes it to work again, so its not that big of a deal, its just really interesting lol
2021-05-28 07:31:18 +0200 <jg> I'll keep tinkering this weekend, but I can live with it for now, I appreciate the help xacktm, I'll let you know if I figure something out, I might ask jaor in the github
2021-05-28 07:32:17 +0200 <xacktm> ok, at least you found a workaround; can't say I'm seeing those symptoms in 0.15 as if I hide the status bar, then recompile, it's still hidden :/
2021-05-28 07:32:29 +0200 <jg> oh yea, my 0.15 has no issues
2021-05-28 07:33:04 +0200 <jg> but I'm doing it differently than in 0.15, I'm using the new Hook.StatusBar
2021-05-28 07:33:45 +0200 <xacktm> ah idk how that works
2021-05-28 07:33:55 +0200 <jg> https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Hooks/StatusBar.hs
2021-05-28 07:34:05 +0200 <jg> check it out, I think its pretty nifty
2021-05-28 07:35:09 +0200 <jg> lmfao xacktm, I just looked deeper, they mention the problem lol let me see if it says a solution
2021-05-28 07:35:34 +0200 <xacktm> nice lol, at least it's known
2021-05-28 07:36:01 +0200 <jg> maybe, they did a work around to restart xmobar, which might be causing the issue
2021-05-28 07:39:15 +0200 <jg> I'm at a loss, goodnight dog
2021-05-28 07:39:31 +0200 <xacktm> kk gngl
2021-05-28 07:40:04 +0200 <xacktm> sorry, games-speak is invading my vocab: good night and good luck!
2021-05-28 07:40:52 +0200jg(~jg@47.149.222.98) (Quit: Client closed)
2021-05-28 07:45:14 +0200 <Solid> xacktm: withEasySB already includes the docks combinator
2021-05-28 07:46:24 +0200 <xacktm> ah oops, so it should've kept the status bar hidden on his first config
2021-05-28 08:10:32 +0200wonko(~wjc@62.115.229.50)
2021-05-28 08:51:11 +0200 <spider_> so.. has there a discussion on whats going to happen with the wayland situation
2021-05-28 08:57:11 +0200 <spider_> nvm gotta go
2021-05-28 09:17:34 +0200qbt(~edun@user/edun) (Ping timeout: 248 seconds)
2021-05-28 09:23:10 +0200qbt(~edun@user/edun)
2021-05-28 09:46:22 +0200qbt(~edun@user/edun) (Ping timeout: 248 seconds)
2021-05-28 09:59:32 +0200mc47(~yecinem@89.246.239.190)
2021-05-28 09:59:32 +0200benin(~benin@183.82.177.19) (Remote host closed the connection)
2021-05-28 10:38:18 +0200cfricke(~cfricke@user/cfricke)
2021-05-28 11:16:47 +0200themainman(~themainma@user/themainman)
2021-05-28 11:25:50 +0200lambdabot(~lambdabot@haskell/bot/lambdabot) (Quit: bbiab)
2021-05-28 11:28:06 +0200lambdabot(~lambdabot@haskell/bot/lambdabot)
2021-05-28 12:03:05 +0200a6a45081-2b83(~aditya@106.212.79.20)
2021-05-28 13:14:30 +0200a6a45081-2b83(~aditya@106.212.79.20) (Quit: Konversation terminated!)
2021-05-28 13:19:31 +0200Tomurb(~tom@158.194.92.121)
2021-05-28 13:24:50 +0200Tomurb(~tom@158.194.92.121) (Ping timeout: 264 seconds)
2021-05-28 13:25:44 +0200utis(~utis@cm-84.214.179.98.getinternet.no) (Quit: leaving)
2021-05-28 13:30:09 +0200autophagy(~mika@user/autophagy)
2021-05-28 13:33:15 +0200leeb(~leeb@2001:268:c04f:ba65:425b:d8ff:fe03:4cd) (Ping timeout: 272 seconds)
2021-05-28 13:42:10 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 264 seconds)
2021-05-28 14:00:11 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.1)
2021-05-28 14:33:28 +0200wonko(~wjc@62.115.229.50) (Quit: See You Space Cowboy..)
2021-05-28 14:53:38 +0200berberman_(~berberman@user/berberman)
2021-05-28 14:54:06 +0200berberman(~berberman@user/berberman) (Ping timeout: 248 seconds)
2021-05-28 15:08:06 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 15:14:00 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Remote host closed the connection)
2021-05-28 15:14:15 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 15:18:37 +0200werneta(~werneta@mobile-166-176-56-141.mycingular.net)
2021-05-28 15:40:33 +0200werneta(~werneta@mobile-166-176-56-141.mycingular.net) (Ping timeout: 272 seconds)
2021-05-28 16:06:49 +0200benin(~benin@183.82.177.19)
2021-05-28 16:26:03 +0200seschwar(~seschwar@user/seschwar)
2021-05-28 16:32:38 +0200 <Solid> liskin: what do you think about merging the tutorial so we can already officially link to it on the website/we also have that INSTALL.md document ready for the hordes of Arch users who are showing up here lately :>
2021-05-28 16:35:33 +0200 <liskin> Solid: I think this process (merge the good enough version early and I'll get to it and perfect it later) worked well with the website so go ahead :-)
2021-05-28 16:36:24 +0200 <Solid> nice :)
2021-05-28 16:37:09 +0200 <liskin> I should perhaps try to overcome this obsession of refusing to merge stuff I haven't had time to meticulously review
2021-05-28 16:39:45 +0200 <liskin> on the other hand, the current way of doing things, that is meticulously review stuff from people who can't merge it themselves, and hand write access to people who can be trusted to make good judgement when to seek more review and when to merge, possibly scales better long term
2021-05-28 16:39:47 +0200 <liskin> at least I hope
2021-05-28 16:47:50 +0200 <Solid> I think the current way is fine tbh
2021-05-28 16:48:11 +0200 <Solid> I'm not a fan of the hands-off "merge everything and then frantically push fixes when things break" approach
2021-05-28 16:52:11 +0200 <liskin> yeah, me neither, but there might be a tradeoff somewhere in the middle, something that might be described as "collaborate on a shared codebase", that doesn't necessarily mean we always merge the first attempt
2021-05-28 16:52:28 +0200 <liskin> like the dynamic status bars, that's probably good enough for people to iterate on
2021-05-28 16:53:08 +0200 <liskin> but I haven't tried it yet, so I'm reluctant to sign off on it, so I'm a bottleneck
2021-05-28 16:53:51 +0200 <liskin> (actually, not really, because mc47 does have write to -contrib, so it's not just my fault it's not merged yet :-))
2021-05-28 16:54:40 +0200 <Solid> :D
2021-05-28 16:56:01 +0200 <liskin> which reminds me of the toggle strut issue jg reported here during the night :-(
2021-05-28 16:56:47 +0200jg(~jg@12.218.15.210)
2021-05-28 16:57:12 +0200 <mc47> not a better time to join :))
2021-05-28 16:57:22 +0200 <Solid> hah
2021-05-28 16:57:28 +0200 <liskin> sounded like the old xmobar didn't terminate on and waited until it got another input to show
2021-05-28 16:57:58 +0200 <mc47> I thought I still didn't add dynamicEasySBs, but apaprently I did, so we could just merge it
2021-05-28 16:58:47 +0200 <mc47> the only issue there is the composability with #460, but we could take care of it afterwards
2021-05-28 16:59:01 +0200 <jg> Y’all run into an issue with the new xmonad statusbar hook where when you —restart the xmobarwno longer behaves struts until opening a window. I might make a github post but not sure if I should put it on xmonad contrib or xmobar
2021-05-28 16:59:24 +0200 <liskin> jg: hey here's a crazy idea: do you have any sensitive data on that VM of yours? there are apparently two issues that we're interested in understanding, so if you just give us the VM in the broken state then we can dig right into it :-)
2021-05-28 16:59:59 +0200mc47has also been spending a lot of time on his thesis... writing a linter without constructing an AST was quite the challenge
2021-05-28 17:00:16 +0200 <jg> Nah I got nothin on it I could install SSH later. I got around my issue with the degree symbol by using Unicode directly recommended by jaor
2021-05-28 17:01:10 +0200 <liskin> I thought you'd just send the disk image itself, as doing graphical stuff over ssh will be a bit painful
2021-05-28 17:01:58 +0200 <liskin> mc47: why not construct an AST? trying to do single-pass constant-memory stuff?
2021-05-28 17:02:21 +0200 <jg> Oh yea I could totally do that when I get home! What are the issues you’re trying to find or y’all are just being hella nice haha! And how would I share it with y’all ?
2021-05-28 17:03:18 +0200 <mc47> liskin it's not really worth it, and it's also kinda useless, since you can define new syntax on the fly (isabelle enables you to do some really wacky stuff)
2021-05-28 17:04:00 +0200 <mc47> And the grammar is a bit complicated
2021-05-28 17:05:30 +0200 <mc47> the middle ground we're going with is to implement the lints themselves as parser combinators, and provide combinators for the most common syntactical constructs... that way you can easily add new lint types, and I won't have to parse the whole grammar
2021-05-28 17:06:10 +0200 <liskin> jg: the xmobar encoding issue because I'm just really nice and really curious what the root cause is and I want to know what to tell the next person who comes with the same problem; and then the toggle struts issue, because that might be a real problem of X.H.StatusBar that we want fixed before the release
2021-05-28 17:06:49 +0200 <liskin> and how to share, hm, that's a good question
2021-05-28 17:07:17 +0200 <jg> I could probably upload to dropbox maybe and share it. I’m not sure of file size limitations
2021-05-28 17:07:44 +0200 <liskin> yeah a dropbox or google drive should work if you have enough free capacity there
2021-05-28 17:08:02 +0200 <liskin> google drive has no limitations on single file sizes as far as I know
2021-05-28 17:08:24 +0200 <liskin> if you compress the disk image it's not going to be more than a gig anyway
2021-05-28 17:09:45 +0200 <jg> yea I can try to figure it out and get that to you. I really appreciate it. That statsbar hook y’all made is really something though beyond that little hickup. I thought it was hella cool
2021-05-28 17:10:31 +0200 <jg> Which could totally be on my end too haha and not a problem with the hook
2021-05-28 17:10:31 +0200 <mc47> that's awesome to hear :D
2021-05-28 17:12:12 +0200 <liskin> yeah and it's going to get better with the PR we were just talking about merging :-)
2021-05-28 17:18:58 +0200 <mc47> I'll take a look at it again later or tomorrow, and merge it if that's okay
2021-05-28 17:19:19 +0200 <mc47> That way people can use and we can get a broader feedback
2021-05-28 17:19:23 +0200 <jg> What’s the PR? I missed that part haha
2021-05-28 17:19:39 +0200 <mc47> We could also wait a bit liskin, if you really want to try it before merging :D
2021-05-28 17:19:44 +0200 <mc47> jq: https://github.com/xmonad/xmonad-contrib/pull/463
2021-05-28 17:20:34 +0200 <mc47> status bars that react to changes in the monitor configuration (plugging-in/out)
2021-05-28 17:21:51 +0200 <jg> Oh that’s dope. I take it that would work for dual monitor setups too? As in I have a script that turns off my second monitor when playing games so I can use gsync. However even when I have 1 monitor on, it used to still spawn 2 xmonars with the spawnpipe
2021-05-28 17:22:19 +0200 <jg> At least both showed up in htop
2021-05-28 17:22:51 +0200 <mc47> yeah that's why I created it, I have the tendency to plug-out my external monitor and lay on my bed sometimes, and it was a bit annoying that xmobar doesn't react to that
2021-05-28 17:23:16 +0200 <mc47> so yeah, if you turn off your second monitor, xmobar will die with it, if you turn it on again, it'll respawn
2021-05-28 17:25:18 +0200 <liskin> mc47: I just went through the diff and have just one minor comment: might be nice to explicitly mention that the active bar tracking (remembering) uses the command line as a key
2021-05-28 17:25:51 +0200 <liskin> just so that when people accidentally spawn two xmobars without parameters, they can read a bit more and find out what's wrong
2021-05-28 17:25:59 +0200 <mc47> Oh that's a good point
2021-05-28 17:26:04 +0200 <liskin> otherwise it's really good to go
2021-05-28 17:26:14 +0200 <mc47> I remember we talked about this issue
2021-05-28 17:26:39 +0200 <liskin> I'll plug in X.H.Rescreen later, but there's no reason to delay the merge any further
2021-05-28 17:28:07 +0200 <liskin> I had this idea that with the extensible conf stuff, we could possibly resurrect the old "statusBar" api because now it would compose safely, but it may be best to just push for dynamicSBs to be the primary way users use this
2021-05-28 17:28:36 +0200 <liskin> anyway no need to worry about that now
2021-05-28 17:29:16 +0200 <liskin> just wanted to plant some seeds so that a month later when I get to it, you guys will have it figured out
2021-05-28 17:29:41 +0200 <jg> mc47 Let me know when I can test that out haha I’d love to give it a spin
2021-05-28 17:29:52 +0200 <mc47> sounds reasonable
2021-05-28 17:30:06 +0200 <mc47> jq I'll add liskin's comment and merge later tonight
2021-05-28 17:30:55 +0200 <liskin> jg: don't forget to back up your vms disk before going too far in that direction, I'll it to be as broken as it is now :-)
2021-05-28 17:31:05 +0200 <liskin> *'ll need it …
2021-05-28 17:31:24 +0200 <jg> Oh heck yea, I should get off work in 6 ish hours. And the I’ll have that disk for you liskin. If I do tinker I’ll clone my disk in its current state before hand
2021-05-28 17:31:53 +0200 <jg> I wonder if discord ha a file size limit lol
2021-05-28 17:31:55 +0200 <jg> has
2021-05-28 17:33:17 +0200 <jg> liskin I forget who but someone linked a bug with gcc the other day that prevents it from being able to compile the Alsa flag in xmobar I’m not sure if you were aware of that. At least I can’t on version 11.1
2021-05-28 17:34:02 +0200 <liskin> jg: I saw that probably but decided that's outside of my area of expertise/interest
2021-05-28 17:34:42 +0200 <liskin> (I don't personally use volume indicators, my laptop has a mute led and that's all I need)
2021-05-28 17:34:43 +0200 <jg> Would jaor care much or probably not? I don’t need it lol
2021-05-28 17:35:07 +0200 <jg> i can make a little post for them if you think it would be beneficial
2021-05-28 17:35:50 +0200 <liskin> might be worth reporting to xmobar/issues
2021-05-28 17:36:26 +0200 <geekosaur> well, the bug wasn't in xmobar per se, it ws in one of the dependencies
2021-05-28 17:41:24 +0200 <geekosaur> hm, might be https://github.com/ttuegel/alsa-mixer/issues/7
2021-05-28 17:41:56 +0200 <geekosaur> although it's not quite the same error message ("'#' doesn't belong here")
2021-05-28 17:42:25 +0200 <jg> Yea the error mentioned something with the C library or something if I remember right
2021-05-28 17:43:19 +0200 <jg> Idk I use a dac So my volume is always at 100 lol
2021-05-28 17:47:09 +0200werneta(~werneta@mobile-166-176-57-62.mycingular.net)
2021-05-28 17:52:09 +0200Tomurb(~tom@158.194.92.121)
2021-05-28 18:08:46 +0200Tomurb(~tom@158.194.92.121) (Ping timeout: 248 seconds)
2021-05-28 18:22:05 +0200 <mc47> alright, #463 is only a proof-read and a squash away from merge
2021-05-28 18:25:28 +0200a6a45081-2b83(~aditya@106.212.79.20)
2021-05-28 18:27:38 +0200benin8(benin@gateway/vpn/protonvpn/benin)
2021-05-28 18:29:04 +0200benin(~benin@183.82.177.19) (Ping timeout: 264 seconds)
2021-05-28 18:29:05 +0200benin8benin
2021-05-28 18:37:43 +0200benin5(~benin@183.82.177.19)
2021-05-28 18:39:42 +0200benin(benin@gateway/vpn/protonvpn/benin) (Ping timeout: 248 seconds)
2021-05-28 18:39:42 +0200benin5benin
2021-05-28 18:44:32 +0200a6a45081-2b83(~aditya@106.212.79.20) (Quit: Konversation terminated!)
2021-05-28 18:44:55 +0200a6a45081-2b83(~aditya@106.212.79.20)
2021-05-28 18:45:36 +0200 <mc47> oh wow that ci speedup is so good!
2021-05-28 18:48:00 +0200 <liskin> is is really that different?
2021-05-28 18:48:08 +0200 <liskin> the stack workflow is still 4 minutes
2021-05-28 18:48:29 +0200 <mc47> I felt it is, I think we were around 7-10 minutes before it
2021-05-28 18:51:56 +0200 <liskin> if you get unlucky and don't hit any caches :-)
2021-05-28 18:54:37 +0200 <liskin> anyway, would be nice if the tutorial was linked from https://github.com/xmonad/xmonad#readme
2021-05-28 18:54:50 +0200 <liskin> that README is like 10 years out of date :-(
2021-05-28 18:56:00 +0200 <jg> liskin I can try and draft up some stack install instructions for arch if it would help
2021-05-28 18:56:20 +0200tremon(~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl)
2021-05-28 18:57:25 +0200 <liskin> jg: there are stack install instructions in the INSTALL.md already
2021-05-28 18:57:51 +0200 <liskin> wouldn't hurt if someone who recently did it checked them though
2021-05-28 18:59:08 +0200 <jg> yea I can take a look! I think it has some stuff for Debian based systems. It would be to add like maybe a line for arch of just yay -S static-stack to avoid most of arches issues
2021-05-28 18:59:44 +0200 <liskin> makes sense, yeah
2021-05-28 19:02:39 +0200 <jg> Oooh the x11 thing got added I havet looked at this in a little ! Or maybe I glanced over it
2021-05-28 19:03:54 +0200dmwit(~dmwit@pool-173-66-86-32.washdc.fios.verizon.net) (Ping timeout: 264 seconds)
2021-05-28 19:05:44 +0200dmwit(~dmwit@pool-173-66-86-32.washdc.fios.verizon.net)
2021-05-28 19:20:48 +0200a6a45081-2b83(~aditya@106.212.79.20) (Read error: Connection reset by peer)
2021-05-28 19:28:35 +0200 <liskin> Solid: btw, I ended up doing https://github.com/liskin/xmonad-web/commit/02e3aa11ecf351fb61852b72499e58d7e0152d1b because GEM_HOME reuses gems installed in the system, and that sometimes breaks (I had to bisect github-pages yesterday and it just crashed on most versions)
2021-05-28 19:28:51 +0200 <liskin> Solid: so this is basically what your README does, just automated
2021-05-28 19:29:03 +0200 <liskin> and the --livereload is really nice :-)
2021-05-28 19:29:39 +0200 <liskin> together with https://github.com/liskin/xmonad-web/commit/08b9354535d9a61a612a8ef605a160eb79f20da9, which mc47 will like (speedup!) that gives almost wysiwyg-like experience :-)
2021-05-28 19:31:25 +0200tekul(~tekul@82-68-220-238.dsl.in-addr.zen.co.uk)
2021-05-28 19:42:39 +0200 <mc47> that's awesome! I'm glad we didn't go with hakyll
2021-05-28 20:28:30 +0200jg(~jg@12.218.15.210) (Quit: Client closed)
2021-05-28 20:38:26 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Remote host closed the connection)
2021-05-28 20:42:23 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 20:47:10 +0200werneta(~werneta@mobile-166-176-57-62.mycingular.net) (Ping timeout: 248 seconds)
2021-05-28 20:49:17 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-28 22:20:23 +0200hexo(~hexo@2a02-ab04-2843-9500-f500-21ca-2d75-caa5.dynamic.v6.chello.sk) (Ping timeout: 272 seconds)
2021-05-28 22:21:14 +0200hexo(~hexo@2a02-ab04-2843-9500-ec04-cc31-4c52-25d9.dynamic.v6.chello.sk)
2021-05-28 22:21:51 +0200jgGuest54(~jgGuest54@47.149.222.98)
2021-05-28 22:22:12 +0200jgGuest54jg
2021-05-28 22:22:33 +0200 <jg> liskin, I am going to try and package it up for you if youre still on
2021-05-28 22:23:52 +0200 <liskin> jg: I'm still on
2021-05-28 22:24:11 +0200 <liskin> not sure I'll get to the actual investigation but I can grab it and try booting it
2021-05-28 22:25:11 +0200 <jg> oh no worries at all, I just wanted to make sure you got it, there is absolutely no rush
2021-05-28 22:27:00 +0200 <jg> I am exporting right now and then I will try and set up a folder
2021-05-28 22:30:08 +0200allbery_b(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-05-28 22:32:14 +0200geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 248 seconds)
2021-05-28 22:32:38 +0200jg(~jgGuest54@47.149.222.98) (Quit: Client closed)
2021-05-28 22:32:48 +0200allbery_bgeekosaur
2021-05-28 22:35:03 +0200jg(~jrgiacone@47.149.222.98)
2021-05-28 22:39:41 +0200 <jg> libskin would you prefer a link or to the drive folder or an email invite
2021-05-28 22:40:22 +0200 <jg> liskin*
2021-05-28 22:41:45 +0200Guest9344(~Guest93@47.149.222.98)
2021-05-28 22:41:51 +0200 <liskin> jg: a link but don't care really
2021-05-28 22:42:30 +0200 <liskin> if you post it here it'll be logged for eternity; but then you'll presumably delete it anyway so …
2021-05-28 22:43:14 +0200 <jg> lmao fair, whatever you think is best
2021-05-28 22:52:00 +0200 <mc47> jq I just merged the PR we were talking about, so you can gladly give it a try and tell us what you think
2021-05-28 22:52:06 +0200jg(~jrgiacone@47.149.222.98) (Ping timeout: 244 seconds)
2021-05-28 22:52:30 +0200Guest9344(~Guest93@47.149.222.98) (Ping timeout: 250 seconds)
2021-05-28 22:54:08 +0200jg(~jrgiacone@47.149.222.98)
2021-05-28 22:54:36 +0200 <geekosaur> <mc47> jq I just merged the PR we were talking about, so you can gladly give it a try and tell us what you think
2021-05-28 22:58:25 +0200 <jg> geekosaur, Yea I can try and take a look, it is in the X.M.StatusBar correct?
2021-05-28 22:59:43 +0200 <geekosaur> I believe so, yes
2021-05-28 23:00:26 +0200 <mc47> yes, if you know how to generate the documentation, it's under Dynamic Status bars
2021-05-28 23:00:42 +0200 <mc47> (stack haddock would generate the docks, for example)
2021-05-28 23:01:05 +0200 <jg> mc47 lol I don't know how, I've just been reading through the comments on github
2021-05-28 23:01:35 +0200 <mc47> that's tedious lol
2021-05-28 23:01:50 +0200 <jg> I am a bit of a newb...
2021-05-28 23:02:16 +0200 <liskin> might be a nice little project to publish latest haddocks from github actions
2021-05-28 23:02:39 +0200 <mc47> if you're using stack, just run `stack haddock` inside your cloned xmonad-contrib repo, and at the end of the logs you'll find a link to the html documentation
2021-05-28 23:02:44 +0200 <liskin> (well, "nice" and "little" might not turn out to be accurate, though :-))
2021-05-28 23:03:03 +0200 <geekosaur> we used to publish them to the wiki years ago,m then switched to just pointing to hackage
2021-05-28 23:03:06 +0200 <jg> ooh let me launch the vm and try
2021-05-28 23:03:22 +0200 <liskin> geekosaur: actually they were part of the website not that long ago
2021-05-28 23:03:32 +0200 <mc47> hmm, is there something like "artifacts" in github actions?
2021-05-28 23:03:51 +0200 <liskin> mc47: https://docs.github.com/en/actions/guides/storing-workflow-data-as-artifacts
2021-05-28 23:04:09 +0200 <liskin> dunno if you can host a bunch of html pages from that, though
2021-05-28 23:04:27 +0200 <liskin> there are all sorts of security implications if they allow that
2021-05-28 23:04:35 +0200 <mc47> interesting
2021-05-28 23:04:35 +0200 <geekosaur> and all of this reminds me that originally I was going to work on migrating the wiki this week, before the freenode shitstorm
2021-05-28 23:04:50 +0200 <jg> running stack haddock rn its almost done
2021-05-28 23:06:33 +0200 <jg> mc47, i cd'd to my xmonad-contrib folder and ran stack haddock, what should I be looking for after
2021-05-28 23:07:02 +0200 <jg> jk i font the doc folder
2021-05-28 23:07:11 +0200 <mc47> you should see a bunch of links to the documentation
2021-05-28 23:08:34 +0200 <jg> these are links to the .16 stuff though, is this current with the commit made?
2021-05-28 23:09:04 +0200 <mc47> haven't you checked out the master branch?
2021-05-28 23:09:14 +0200 <mc47> you might need to run `git pull`
2021-05-28 23:09:35 +0200 <jg> ah i just cloned the repo via 'git clone'
2021-05-28 23:10:24 +0200 <jg> liskin, it shoud be uploaded to that folder, lmk if i need to relink it
2021-05-28 23:10:35 +0200 <jg> I included the iso with it
2021-05-28 23:17:31 +0200tekul(~tekul@82-68-220-238.dsl.in-addr.zen.co.uk) (Quit: Client closed)
2021-05-28 23:21:27 +0200 <jg> mc47 after I git pull in each folder I just re-run stack install correct?
2021-05-28 23:21:51 +0200 <mc47> not sure how you've set it up
2021-05-28 23:21:59 +0200 <jg> lol ill just send it
2021-05-28 23:22:16 +0200 <mc47> but if you followed the tutorial, stack build should do its job i guess
2021-05-28 23:22:19 +0200 <jg> git pulled all 3, stack update, stack install lol
2021-05-28 23:22:35 +0200 <mc47> you don't need stack update
2021-05-28 23:22:43 +0200 <mc47> you actually just need to run stack build in your xmonad repo
2021-05-28 23:22:47 +0200 <mc47> (probably)
2021-05-28 23:23:03 +0200 <jg> good to know for future lol i'll just brute force it, I gave this vm 8 cores so it shouldnt take to long
2021-05-28 23:23:53 +0200 <mc47> (the difference between stack build and stack install, is that stack install just does stack build and symlinks the binary)
2021-05-28 23:27:20 +0200 <jg> geekosaur I am just trying to figure out how to extend vm to my second screen
2021-05-28 23:29:55 +0200 <liskin> jg: it's 0.16 because we haven't bumped the version yet
2021-05-28 23:30:04 +0200 <liskin> so git master still builds as 0.16
2021-05-28 23:31:20 +0200jg(~jrgiacone@47.149.222.98) (Quit: Lost terminal)
2021-05-28 23:33:11 +0200jg(~jrgiacone@47.149.222.98)
2021-05-28 23:33:21 +0200 <jg> accidently closed my X11 lmfao
2021-05-28 23:34:15 +0200 <liskin> jg: re folder, I haven't seen the link anywhere; if you posted it around 22:53:00 CEST (20:53 UTC) you dropped out at the time
2021-05-28 23:35:26 +0200 <jg> liskin here you go big dog: https://drive.google.com/drive/folders/1k5kJgxSkWgV_in2s6jIdJY5czedxtTqc?usp=sharing
2021-05-28 23:38:39 +0200 <liskin> jg: okay, downloading
2021-05-28 23:48:42 +0200 <jg> geekosaur, i got my vm to display both monitors, do i need to create two spawn pipes like in .15 for the xmobar to display on both screens. at the moment, it does not detect my second screen to generate another bar on its own
2021-05-28 23:49:42 +0200 <geekosaur> jg, I was just forwarding mc47 said just before IRC told us you'd fallen out of the channel again; I have little to do with the dynamic status bar stuff. But my understanding is that if it's configured correctly it should be automatic
2021-05-28 23:50:20 +0200 <geekosaur> (It does require configuration, not everyone wants multiple statusbars just because they have multiple monitors.)
2021-05-28 23:51:03 +0200 <jg> hmmmm, I used the withEasySB (statusBarProp "xmobar" (pure myXmobarPP)) defTogleStrutsKey, but I was not prompeted with anything
2021-05-28 23:51:20 +0200 <mc47> that should create one status bar
2021-05-28 23:51:25 +0200 <jg> ahh
2021-05-28 23:51:35 +0200 <jg> so its a me problem
2021-05-28 23:52:01 +0200 <mc47> if you want more, you can either compose them with <>, or use dynamicSBs (or dynamicEasySBs)
2021-05-28 23:52:36 +0200 <jg> like create a withSB section like hsown around line 252?
2021-05-28 23:52:54 +0200manuel__(~manuel@185.68.78.228)
2021-05-28 23:53:23 +0200 <mc47> not sure about the line, but yeah
2021-05-28 23:53:41 +0200 <mc47> if you're looking at the source, the docs start at line 376
2021-05-28 23:53:56 +0200manuel__(~manuel@185.68.78.228) (Client Quit)
2021-05-28 23:54:25 +0200 <jg> mc47, I am looking at the StatusBar.hs on github
2021-05-28 23:54:38 +0200 <jg> i have a feeling im in the wrong spot
2021-05-28 23:55:15 +0200 <mc47> https://github.com/xmonad/xmonad-contrib/blob/master/XMonad/Hooks/StatusBar.hs#L375
2021-05-28 23:56:27 +0200 <jg> lit, reading now