2021/02/11

2021-02-11 01:24:03 +0100notis(~notis@185.51.134.229) (Ping timeout: 256 seconds)
2021-02-11 01:32:07 +0100thc202(~thc202@unaffiliated/thc202) (Ping timeout: 260 seconds)
2021-02-11 01:48:48 +0100tremon(~aschuring@217-63-61-89.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
2021-02-11 02:41:41 +0100gazler_(~gazler@195.107.2.81.in-addr.arpa)
2021-02-11 02:42:11 +0100gazler__(~gazler@2001:8b0:b165:a8d2:d19:fc83:e0fa:4af3) (Read error: Connection reset by peer)
2021-02-11 02:45:37 +0100growpotk-(~growpotki@130-45-30-154.dyn.grandenetworks.net)
2021-02-11 02:58:08 +0100growpotk|(~growpotki@130-45-30-154.dyn.grandenetworks.net)
2021-02-11 02:58:30 +0100growpotk-(~growpotki@130-45-30-154.dyn.grandenetworks.net) (Read error: Connection reset by peer)
2021-02-11 03:27:50 +0100materiyolo(~materiyol@112.204.169.246)
2021-02-11 03:28:34 +0100abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Remote host closed the connection)
2021-02-11 03:55:03 +0100growpotk|(~growpotki@130-45-30-154.dyn.grandenetworks.net) (Ping timeout: 246 seconds)
2021-02-11 04:01:05 +0100materiyolo(~materiyol@112.204.169.246) (Quit: WeeChat 2.9)
2021-02-11 04:04:45 +0100theDon(~td@muedsl-82-207-238-226.citykom.de) (Ping timeout: 264 seconds)
2021-02-11 04:06:16 +0100theDon(~td@muedsl-82-207-238-223.citykom.de)
2021-02-11 05:02:47 +0100theDon(~td@muedsl-82-207-238-223.citykom.de) (Ping timeout: 256 seconds)
2021-02-11 05:04:19 +0100theDon(~td@muedsl-82-207-238-072.citykom.de)
2021-02-11 06:12:41 +0100growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net) (Quit: ZNC 1.8.2 - https://znc.in)
2021-02-11 07:57:55 +0100xaltsc(~xaltsc@unaffiliated/xaltsc)
2021-02-11 07:58:52 +0100palo1(~weechat@c-base/crew/palo)
2021-02-11 08:01:45 +0100palo(~weechat@c-base/crew/palo) (Ping timeout: 240 seconds)
2021-02-11 08:01:46 +0100palo1palo
2021-02-11 09:11:49 +0100mc47(~yecinem@89.246.239.190)
2021-02-11 09:13:46 +0100xaltsc(~xaltsc@unaffiliated/xaltsc) (Quit: WeeChat 3.0)
2021-02-11 09:34:00 +0100everythingTaken(~everythin@gateway/tor-sasl/everythingtaken)
2021-02-11 09:36:35 +0100xaltsc(~xaltsc@unaffiliated/xaltsc)
2021-02-11 09:39:04 +0100notis(~notis@185.51.134.229)
2021-02-11 09:51:35 +0100everythingTaken(~everythin@gateway/tor-sasl/everythingtaken) (Remote host closed the connection)
2021-02-11 10:04:13 +0100materiyolo(~materiyol@112.204.169.246)
2021-02-11 10:31:36 +0100ectospasm(~ectospasm@unaffiliated/ectospasm) (Ping timeout: 246 seconds)
2021-02-11 10:36:41 +0100rotaerk(rotaerk@2600:3c02::f03c:91ff:fe70:4a45) (Ping timeout: 246 seconds)
2021-02-11 10:44:09 +0100ectospasm(~ectospasm@unaffiliated/ectospasm)
2021-02-11 11:08:09 +0100rotaerk(rotaerk@2600:3c02::f03c:91ff:fe70:4a45)
2021-02-11 11:30:31 +0100thc202(~thc202@unaffiliated/thc202)
2021-02-11 11:51:21 +0100materiyolo(~materiyol@112.204.169.246) (Quit: WeeChat 2.9)
2021-02-11 11:59:04 +0100rotaerk(rotaerk@2600:3c02::f03c:91ff:fe70:4a45) (Ping timeout: 240 seconds)
2021-02-11 12:13:17 +0100rotaerk(rotaerk@2600:3c02::f03c:91ff:fe70:4a45)
2021-02-11 12:26:00 +0100materiyolo(~materiyol@112.204.169.246)
2021-02-11 12:41:13 +0100xaltsc(~xaltsc@unaffiliated/xaltsc) (Ping timeout: 256 seconds)
2021-02-11 13:51:38 +0100ericsagn1(~ericsagne@2405:6580:0:5100:5542:a02b:6ef4:719e) (Ping timeout: 246 seconds)
2021-02-11 14:04:21 +0100ericsagn1(~ericsagne@2405:6580:0:5100:b04a:c81a:c281:6323)
2021-02-11 14:08:46 +0100geekosaur(82650c7a@130.101.12.122)
2021-02-11 14:54:22 +0100davemq_(~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net)
2021-02-11 14:54:33 +0100davemq(~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net) (Ping timeout: 264 seconds)
2021-02-11 14:56:40 +0100davemq_(~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net) (Client Quit)
2021-02-11 14:57:53 +0100davemq(~davemq@2600:1700:b1c0:2580::4d8)
2021-02-11 15:12:42 +0100geekosaur(82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
2021-02-11 15:20:39 +0100geekosaur(82650c7a@130.101.12.122)
2021-02-11 15:42:21 +0100growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net)
2021-02-11 15:45:51 +0100seschwar(~seschwar@unaffiliated/seschwar)
2021-02-11 15:57:11 +0100geekosaur(82650c7a@130.101.12.122) (Quit: Connection closed)
2021-02-11 16:21:28 +0100materiyolo(~materiyol@112.204.169.246) (Quit: WeeChat 2.9)
2021-02-11 16:36:55 +0100xaltsc(~xaltsc@unaffiliated/xaltsc)
2021-02-11 16:37:50 +0100hexo(~hexo@gateway/tor-sasl/hexo) (Remote host closed the connection)
2021-02-11 16:38:09 +0100hexo(~hexo@gateway/tor-sasl/hexo)
2021-02-11 16:52:25 +0100eb0t(~eblip@unaffiliated/eblip) (Quit: WeeChat 1.6)
2021-02-11 17:33:01 +0100everythingTaken(~everythin@gateway/tor-sasl/everythingtaken)
2021-02-11 18:05:39 +0100geekosaur(82650c7a@130.101.12.122)
2021-02-11 18:07:50 +0100ericsagn1(~ericsagne@2405:6580:0:5100:b04a:c81a:c281:6323) (Ping timeout: 246 seconds)
2021-02-11 18:08:51 +0100 <geekosaur> mm, did anyone get a notification about the xmonad-testing PR I opened yesterday?
2021-02-11 18:12:16 +0100 <Liskni_si> geekosaur: I did, but I know absolutely nothing about cabal so I don't feel qualified to comment on it
2021-02-11 18:13:08 +0100 <Liskni_si> s/cabal/cabal-install/
2021-02-11 18:15:43 +0100 <geekosaur> ok
2021-02-11 18:16:34 +0100 <geekosaur> I think it's still doing more than one could hope, kinda hard to tell on a system with an SSD :)  but the notice in the README should cover that and it'd apply to stack as well
2021-02-11 18:17:04 +0100 <geekosaur> (basically, the quick recompile check xmonad does is suppressed with a build script because xmonad has no idea what or where the build script is doing things)
2021-02-11 18:18:05 +0100 <geekosaur> it's a few seconds before xmonad starts up, but at least it's not showing an actual recompile going on, so I think it's just building and comparing build plans to what already exists
2021-02-11 18:18:22 +0100nerdthatnoonelik(~nerdthatn@ip206.ip-51-81-119.us)
2021-02-11 18:18:25 +0100 <nerdthatnoonelik> hello everyone
2021-02-11 18:18:35 +0100 <nerdthatnoonelik> I have an issue with xmobar not launching with xmonad
2021-02-11 18:19:06 +0100 <nerdthatnoonelik> xmobar was launching with xmonad just fine but ever since i used a different config its not launching anymore
2021-02-11 18:19:15 +0100 <nerdthatnoonelik> i have to manually launch it from the terminal by running xmobar
2021-02-11 18:20:17 +0100ericsagn1(~ericsagne@2405:6580:0:5100:f37e:89b0:6afc:b223)
2021-02-11 18:20:57 +0100 <geekosaur> are you running xmonad from git by any chance?
2021-02-11 18:21:05 +0100 <geekosaur> otherwise, pastebin your config
2021-02-11 18:21:11 +0100 <geekosaur> @where paste
2021-02-11 18:21:11 +0100 <lambdabot> Help us help you: please paste full code, input and/or output at eg https://paste.tomsmeding.com
2021-02-11 18:24:04 +0100 <nerdthatnoonelik> wdym from git?
2021-02-11 18:24:05 +0100 <nerdthatnoonelik> and ok i will paste my config in a pastebin
2021-02-11 18:24:48 +0100 <geekosaur> we've been overhauling the status bar support as part of preparing for a new release. if that didn't mean anything to you, it's reasonably certain you aren't :)
2021-02-11 18:25:57 +0100 <nerdthatnoonelik> https://paste.tomsmeding.com/EVO15aDf heres my xmobar config
2021-02-11 18:27:44 +0100 <geekosaur> hm. are all the fonts installed, and is your xmobar built with XFT support (should show in "xmobar --help" output)
2021-02-11 18:28:39 +0100 <nerdthatnoonelik> xmobar --help doesn't say anything about xft support and yes all the fonts are installed
2021-02-11 18:29:59 +0100 <Liskni_si> might be a good idea to check the log file for any errors xmobar might have printed
2021-02-11 18:30:09 +0100 <Liskni_si> not that I know which log file in particular
2021-02-11 18:30:42 +0100 <nerdthatnoonelik> my ~/.xmonad/xmonad.errors file doesn't have anything in it except for a deprecation warning
2021-02-11 18:31:07 +0100everythingTaken(~everythin@gateway/tor-sasl/everythingtaken) (Quit: everythingTaken)
2021-02-11 18:31:16 +0100 <geekosaur> that won't be the right file. normally it's either ~/.xsession-errors or something under journalctl
2021-02-11 18:33:05 +0100 <geekosaur> this is somewhat hard for me to debug as I don't run xmobar and have nowhere to put it on this machine (bars along the edges already, but I run mate-panel since I use mate integration with xmonad)
2021-02-11 18:35:50 +0100 <nerdthatnoonelik> ok my xsession-errors has the following errors related to xmobar "xmobar: eof at an early stage"
2021-02-11 18:43:30 +0100 <Solid> so what was the working config/
2021-02-11 18:43:51 +0100 <Solid> (the one that worked)
2021-02-11 18:43:54 +0100 <Solid> nerdthatnoonelik
2021-02-11 18:45:02 +0100 <nerdthatnoonelik> hang on i'll put in a pastebin
2021-02-11 18:45:35 +0100 <nerdthatnoonelik> https://paste.tomsmeding.com/K80zv7Bl
2021-02-11 18:46:21 +0100 <geekosaur> hm, wasn't that error noted as a bug recently? (sadly I don't see a way to search in our logs)
2021-02-11 18:47:13 +0100 <Solid> that error was just some left-over from debugging an issue that has since been removed from xmobar
2021-02-11 18:47:50 +0100 <Solid> nerdthatnoonelik: I can see that you're referring to two different home directories in the new config; is that correct?
2021-02-11 18:48:31 +0100 <nerdthatnoonelik> i changed that
2021-02-11 18:48:39 +0100 <nerdthatnoonelik> but xmobar still won
2021-02-11 18:48:45 +0100 <nerdthatnoonelik> *won't start
2021-02-11 18:53:52 +0100 <nerdthatnoonelik> but i can still start it by running xmobar in the shell
2021-02-11 18:55:23 +0100 <Solid> how are you starting it from within your xmonad config?
2021-02-11 18:57:09 +0100 <nerdthatnoonelik> https://paste.tomsmeding.com/ocDyU12n
2021-02-11 18:59:07 +0100 <Liskni_si> you're not writing anything into that xmproc pipe
2021-02-11 18:59:19 +0100 <nerdthatnoonelik> well that worked for my last xmobar config
2021-02-11 18:59:20 +0100 <Liskni_si> so the garbage collector closes it and xmobar terminates immediately
2021-02-11 18:59:25 +0100 <nerdthatnoonelik> oh
2021-02-11 18:59:37 +0100 <Liskni_si> this config couldn't have worked, ever
2021-02-11 19:00:44 +0100 <geekosaur> not exactly true, whether gc runs in a timely fashion or not depends on ghc / rts version
2021-02-11 19:01:05 +0100 <nerdthatnoonelik> but it did, my last xmobar config worked fine with it, i watched this video about it https://www.youtube.com/watch?v=3noK4GTmyMw and he did the same
2021-02-11 19:01:29 +0100 <Solid> your last xmobar config didn't read from the pipe in any way
2021-02-11 19:01:39 +0100 <Solid> so it didn't matter that you ignored the input
2021-02-11 19:01:55 +0100 <nerdthatnoonelik> oh
2021-02-11 19:04:08 +0100 <nerdthatnoonelik> so how do i get xmobar to not terminate immediately
2021-02-11 19:05:04 +0100 <Solid> you are presumably using `xmproc' in your `default' function?
2021-02-11 19:05:59 +0100 <Solid> so add it as an argument; `defaults xmproc = ...` and call with `xmonad $ docks $ defaults xmproc'
2021-02-11 19:10:48 +0100Solidnow knows why people have this exact problem so often
2021-02-11 19:11:12 +0100 <Solid> this distrotube guy didn't test the configs he showed people in his video :/
2021-02-11 19:12:42 +0100 <geekosaur> everyone does this. they think that just using the pipe magically makes xmonad restart the dock when it's restarted / mod-q
2021-02-11 19:13:23 +0100 <geekosaur> nobody knows or cares how unix pipes work, or FD_CLOEXEC, or when gc happens
2021-02-11 19:14:43 +0100 <Solid> it's not even about that; it's about starting the pipe but then not feeding it to ppOutput at all
2021-02-11 19:15:46 +0100 <geekosaur> yes
2021-02-11 19:15:54 +0100 <geekosaur> I'm telling you why people cargo-cult it
2021-02-11 19:16:08 +0100 <Solid> oh
2021-02-11 19:16:27 +0100 <geekosaur> there is a mis-belief that, just because it's a pipe, xmonad will go hunt down and kill the process on restart
2021-02-11 19:16:57 +0100 <geekosaur> this is part of why the recent DynamicLog changes, so it *will* go hunt things down for users who cargo-cult it
2021-02-11 19:33:31 +0100nerdthatnoonelik(~nerdthatn@ip206.ip-51-81-119.us) (Quit: Lost terminal)
2021-02-11 19:36:04 +0100nerdthatnoonelik(~nerdthatn@ip206.ip-51-81-119.us)
2021-02-11 19:41:16 +0100nerdthatnoonelik(~nerdthatn@ip206.ip-51-81-119.us) (Quit: Lost terminal)
2021-02-11 19:48:10 +0100tremon(~aschuring@217-63-61-89.cable.dynamic.v4.ziggo.nl)
2021-02-11 19:59:48 +0100nerdthatnoonelik(~nerdthatn@ip206.ip-51-81-119.us)
2021-02-11 20:00:04 +0100 <nerdthatnoonelik> So I'm still confused on what im supposed to add to fix xmobar stop closing
2021-02-11 20:00:37 +0100 <nerdthatnoonelik> because I don't know enough about haskell to know what you were talking about
2021-02-11 20:01:28 +0100 <mc47> do you want to feed xmobar data from xmonad or not?
2021-02-11 20:02:18 +0100 <geekosaur> your xmobar config has an unsafeStdinReader in it, which implies your xmonad config should be sending it output including xmobar escapes
2021-02-11 20:02:49 +0100 <nerdthatnoonelik> ah
2021-02-11 20:03:08 +0100 <nerdthatnoonelik> ok i just removed it and it worked, thanks for all the help guys!
2021-02-11 20:03:10 +0100nerdthatnoonelik(~nerdthatn@ip206.ip-51-81-119.us) (Client Quit)
2021-02-11 20:03:17 +0100 <Solid> lol
2021-02-11 20:03:20 +0100 <mc47> hahaha
2021-02-11 20:03:59 +0100 <mc47> "The fastest hand in the West"
2021-02-11 20:04:33 +0100 <Solid> I guess that's the bad thing about a person who doesn't know haskell making that many xmonad videos :>
2021-02-11 20:04:53 +0100 <geekosaur> well, this is someone not knowing POSIX tbh
2021-02-11 20:05:00 +0100 <geekosaur> not specific to Haskell
2021-02-11 20:07:28 +0100 <Solid> good point
2021-02-11 20:07:46 +0100 <Liskni_si> all the knowledge of POSIX has been given away already, there isn't any left, so expecting young people to get some is unreasonable.
2021-02-11 20:08:24 +0100 <Solid> he also copies the default configuration verbatim and modifies that instead of starting from an empty file
2021-02-11 20:08:26 +0100 <Solid> sigh
2021-02-11 20:12:03 +0100 <mc47> to be fair, there aren't a lot of xmonad guides out there
2021-02-11 20:15:22 +0100geekosaur(82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
2021-02-11 20:16:02 +0100 <Solid> that is true
2021-02-11 20:17:16 +0100 <Solid> there already is a good tutorial out there, it just needs to be updated and put directly onto the repo
2021-02-11 20:17:30 +0100Solidshould continue doing that at some point...
2021-02-11 20:18:21 +0100gazler(~gazler@195.107.2.81.in-addr.arpa)
2021-02-11 20:18:36 +0100 <mc47> which tutorial are you referring to, btw?
2021-02-11 20:19:32 +0100 <Solid> https://wiki.haskell.org/Xmonad/Config_archive/John_Goerzen's_Configuration
2021-02-11 20:19:34 +0100 <Solid> that one
2021-02-11 20:19:42 +0100gazler_(~gazler@195.107.2.81.in-addr.arpa) (Ping timeout: 256 seconds)
2021-02-11 20:19:44 +0100 <Solid> it says it's their configuration, but it's really a tutorial
2021-02-11 20:19:51 +0100 <Solid> maybe that's why it's so hard to find :)
2021-02-11 20:20:43 +0100gazler_(~gazler@195.107.2.81.in-addr.arpa)
2021-02-11 20:23:41 +0100gazler(~gazler@195.107.2.81.in-addr.arpa) (Ping timeout: 272 seconds)
2021-02-11 20:25:38 +0100 <mc47> It's pretty good
2021-02-11 20:26:35 +0100 <mc47> eum so I'm writing the docs for the potential "XMonad.Hooks.StatusBar".. Should the module be "aware" that DynamicLog exists?
2021-02-11 20:27:07 +0100gazler(~gazler@195.107.2.81.in-addr.arpa)
2021-02-11 20:27:14 +0100 <Solid> more than that, I think we should officially deprecate DynamicLog
2021-02-11 20:27:20 +0100 <Solid> but I'm a bit extreme in that regard :>
2021-02-11 20:27:42 +0100 <mc47> I mean, should I restate the explanation again on why property logging should be used instead of pipes, or simply refer to DynamicLog?
2021-02-11 20:27:48 +0100 <Liskni_si> I thought those xmobarPPs and strips and so on would stay in DynamicLog
2021-02-11 20:28:09 +0100 <Liskni_si> (brb, dinner)
2021-02-11 20:28:10 +0100 <Solid> oh would they? I thought they'd be moved in that new .PP module
2021-02-11 20:28:20 +0100 <mc47> I moved them to the new .PP module and re-exported
2021-02-11 20:28:51 +0100 <mc47> DynamicLog only has xmobar, statusBar and dzen/dzenWithFlags now
2021-02-11 20:30:08 +0100gazler_(~gazler@195.107.2.81.in-addr.arpa) (Ping timeout: 272 seconds)
2021-02-11 20:30:11 +0100 <Solid> ah well, probably can't deprecate that then
2021-02-11 20:30:35 +0100 <Solid> either way, I don't think we need to duplicate documentation
2021-02-11 20:30:41 +0100 <Solid> you can just link to DynamicLog
2021-02-11 20:34:06 +0100 <Solid> I was gonna say we probably also need to rewrite https://wiki.haskell.org/Xmonad/xmonad_development_tutorial but it still looks pretty good
2021-02-11 20:34:13 +0100 <Solid> may just need to copy that over to some place else
2021-02-11 20:35:56 +0100geekosaur(82650c7a@130.101.12.122)
2021-02-11 20:40:53 +0100notis(~notis@185.51.134.229) (Quit: WeeChat 3.0)
2021-02-11 20:43:17 +0100notis(~notis@185.51.134.222)
2021-02-11 20:46:42 +0100spoonm(~spoonm@gunma.spoonm.org) (Quit: Don't look behind you!)
2021-02-11 20:49:24 +0100spoonm(~spoonm@2602:ffd5:1:119::1)
2021-02-11 20:57:20 +0100 <Liskni_si> oh, that's probably why I wanted the cyclic dependency thing
2021-02-11 20:57:43 +0100 <Liskni_si> because the amount of stuff that DynamicLog needs from StatusBar is way less than the other way around
2021-02-11 20:58:09 +0100 <Liskni_si> now we're essentially renaming DynamicLog aren't we?
2021-02-11 21:00:31 +0100 <Solid> pretty much
2021-02-11 21:09:32 +0100 <Liskni_si> that wasn't really what I thought we'd end up with, but that doesn't mean it's bad; my brain isn't able to foresee all that right now
2021-02-11 21:11:58 +0100 <Liskni_si> what I thought would be good was to somehow separate producing the log string from launching the bars and the rest of the plumbing
2021-02-11 21:12:59 +0100 <geekosaur> that ideally would go with the PP stuff
2021-02-11 21:13:28 +0100 <geekosaur> the problem being the PP contains the plumbing
2021-02-11 21:13:45 +0100 <Liskni_si> but the separation isn't as clear as I'd like it to be, as the log syntax is specific to the bar program, so if we want to provide simple wrappers, those need to import the xmobarPP/dzenPP and its deps
2021-02-11 21:14:10 +0100 <geekosaur> hm, this may mean there's no way to achieve backward compatibility while also avoiding circular references :(
2021-02-11 21:14:59 +0100 <Liskni_si> well there's always a way, we can always create one module per strongly connected component of functions
2021-02-11 21:15:12 +0100 <Liskni_si> but there may be no _nice_ way
2021-02-11 21:17:20 +0100 <Liskni_si> we could maybe have 4 modules: PP stuff; generic plumbing stuff without specific wrappers; specific wrappers that tie it together; and then DynamicLog for compat
2021-02-11 21:17:26 +0100 <Liskni_si> no idea if all that's worth it
2021-02-11 21:17:55 +0100 <Liskni_si> DynamicLog could be "specific wrappers" module
2021-02-11 21:18:54 +0100 <Liskni_si> on the other hand having a module like StatusBar with clean interface is nice, too
2021-02-11 21:28:25 +0100 <Solid> maybe PP+plumbing, pipes, properties?
2021-02-11 21:43:56 +0100davemq(~davemq@2600:1700:b1c0:2580::4d8) (Ping timeout: 240 seconds)
2021-02-11 21:48:59 +0100davemq(~davemq@2600:1700:b1c0:2580::4d8)
2021-02-11 22:28:34 +0100endiruna(~endiendir@46.101.187.207) (Ping timeout: 272 seconds)
2021-02-11 22:33:10 +0100 <mc47> a bit late to the party, but I guess it makes a bit sense to structure the modules around a data structure
2021-02-11 22:33:36 +0100mc47(~yecinem@89.246.239.190) (Quit: Leaving)
2021-02-11 22:33:58 +0100mc47(~yecinem@89.246.239.190)
2021-02-11 22:35:00 +0100 <mc47> I kinda thought of .PP to contain the example formatters and the formatting utilities (wrap, pad ..)
2021-02-11 22:35:20 +0100 <Liskni_si> Solid: if plumbing includes the multiple bar stuff, I think it's probably best to separate from the PP stuff
2021-02-11 22:35:47 +0100 <Liskni_si> it gets too long otherwise (it wouldn't without the documentation, but then it'd be useless)
2021-02-11 22:35:48 +0100 <mc47> StatusBar for creating, composing, managing and binding the StatusBarConfig's
2021-02-11 22:36:37 +0100 <mc47> and DynamicLog for the statusBar, xmobar and dzen*
2021-02-11 22:37:18 +0100 <Liskni_si> maybe that's best after all
2021-02-11 22:37:26 +0100 <Liskni_si> we just need a good name for the PP module
2021-02-11 22:37:45 +0100 <mc47> The only thing that doesn't quite fit is the dynamicLog* functions.. I've put them inside .PP to avoid the circular imports, but it could be argued that we put them in DynamicLog
2021-02-11 22:38:13 +0100mc47is terrible with names
2021-02-11 22:38:26 +0100 <Liskni_si> well dynamicLogString definitely belongs close to PP
2021-02-11 22:38:54 +0100 <Liskni_si> and the other two too
2021-02-11 22:39:16 +0100 <Liskni_si> dynamicLogXinerama is some weird leftover crap
2021-02-11 22:39:29 +0100 <Liskni_si> who runs xmonad actually piped to dzen/xmobar?
2021-02-11 22:39:53 +0100 <Liskni_si> so that one goes to the compat module
2021-02-11 22:40:17 +0100endiruna(~endiendir@46.101.187.207)
2021-02-11 22:40:29 +0100 <Liskni_si> (I mean someone probably does because if it worked 10 years ago it still works now, so we may not want to break it without a good replacement)
2021-02-11 22:41:00 +0100 <mc47> which one do you mean?
2021-02-11 22:41:02 +0100 <geekosaur> xmonad 0.3!
2021-02-11 22:41:57 +0100 <Liskni_si> mc47: which one I mean by which sentence? :-)
2021-02-11 22:42:38 +0100 <mc47> what goes inside the compact module? And which one is the compact module again? :D
2021-02-11 22:43:05 +0100 <geekosaur> compat(ibility) module
2021-02-11 22:43:07 +0100 <geekosaur> not compact
2021-02-11 22:43:24 +0100 <mc47> Oh, that makes sense now
2021-02-11 22:43:32 +0100 <geekosaur> DynamicLog, as distinct from StatusBar, with the current proposal
2021-02-11 22:55:55 +0100geekosaur(82650c7a@130.101.12.122) (Quit: Connection closed)
2021-02-11 23:06:27 +0100xaltsc(~xaltsc@unaffiliated/xaltsc) (Ping timeout: 272 seconds)
2021-02-11 23:06:52 +0100endiruna(~endiendir@46.101.187.207) (Ping timeout: 256 seconds)
2021-02-11 23:08:24 +0100endiruna(~endiendir@46.101.187.207)
2021-02-11 23:16:45 +0100endiruna(~endiendir@46.101.187.207) (Ping timeout: 264 seconds)
2021-02-11 23:19:50 +0100endiruna(~endiendir@46.101.187.207)
2021-02-11 23:36:08 +0100davemq(~davemq@2600:1700:b1c0:2580::4d8) (Quit: ZNC 1.8.2 - https://znc.in)
2021-02-11 23:37:10 +0100davemq(~davemq@2600:1700:b1c0:2580::4d8)
2021-02-11 23:46:59 +0100davemq(~davemq@2600:1700:b1c0:2580::4d8) (Ping timeout: 272 seconds)
2021-02-11 23:47:41 +0100davemq(~davemq@99-179-0-50.lightspeed.austtx.sbcglobal.net)