2021/03/04

2021-03-04 00:00:57 +0100unrooted_(~unrooted@user-5-173-8-8.play-internet.pl) (Read error: Connection reset by peer)
2021-03-04 00:13:16 +0100mc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-03-04 00:35:45 +0100Steven_M(~Steven_M@unaffiliated/steven-m/x-3557666)
2021-03-04 00:42:04 +0100 <Steven_M> Hi all, is xmonad-contrib available for FreeBSD?
2021-03-04 01:03:45 +0100 <vrs> it used to be when I ran it, which was 2014-ish
2021-03-04 01:14:31 +0100evanjs(~evanjs@075-129-098-007.res.spectrum.com) (Read error: Connection reset by peer)
2021-03-04 01:16:59 +0100evanjs(~evanjs@075-129-098-007.res.spectrum.com)
2021-03-04 01:34:38 +0100notis(~notis@185.51.134.230) (Read error: Connection reset by peer)
2021-03-04 01:40:00 +0100toniz4(~toniz4@unaffiliated/toniz4) (Quit: bye)
2021-03-04 01:53:55 +0100st13g_st13g
2021-03-04 02:08:49 +0100 <Steven_M> vrs: oh, I can't find the port for it.
2021-03-04 02:10:46 +0100 <vrs> they apparently removed it? https://www.freshports.org/x11-wm/hs-xmonad-contrib
2021-03-04 02:10:57 +0100 <vrs> I don't quite understand why
2021-03-04 02:12:02 +0100 <vrs> https://forums.freebsd.org/threads/what-happened-to-xmonad-contrib-and-some-other-gripes.77203/
2021-03-04 02:12:44 +0100 <vrs> I don't know if cabal or stack is currently the recommended way?
2021-03-04 02:17:04 +0100 <Steven_M> okay, thanks for the info. :)
2021-03-04 02:17:52 +0100 <Steven_M> vrs: see above
2021-03-04 02:18:10 +0100 <vrs> saw
2021-03-04 02:47:06 +0100adamik(~nodelet@unaffiliated/adamik) (Quit: leaving)
2021-03-04 03:21:53 +0100def_jameblip
2021-03-04 03:33:29 +0100pharaun(~pharaun@static.88-198-62-245.clients.your-server.de) (Ping timeout: 256 seconds)
2021-03-04 03:44:12 +0100pharaun(~pharaun@static.88-198-62-245.clients.your-server.de)
2021-03-04 03:53:14 +0100Steven_M(~Steven_M@unaffiliated/steven-m/x-3557666) (Quit: busy)
2021-03-04 04:43:21 +0100theDon(~td@muedsl-82-207-238-151.citykom.de) (Ping timeout: 246 seconds)
2021-03-04 04:45:17 +0100theDon(~td@94.134.91.49)
2021-03-04 05:04:04 +0100dxld(~dxld@rush.pub.dxld.at) (Ping timeout: 240 seconds)
2021-03-04 05:05:50 +0100dxld(~dxld@80-109-136-248.cable.dynamic.surfer.at)
2021-03-04 05:59:03 +0100materiyolo(~materiyol@112.204.160.151)
2021-03-04 07:11:04 +0100palo1(~weechat@c-base/crew/palo)
2021-03-04 07:14:29 +0100palo(~weechat@c-base/crew/palo) (Ping timeout: 256 seconds)
2021-03-04 07:14:29 +0100palo1palo
2021-03-04 07:19:50 +0100growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net) (Quit: ZNC 1.8.2 - https://znc.in)
2021-03-04 08:10:28 +0100cfricke(~cfricke@unaffiliated/cfricke)
2021-03-04 09:20:38 +0100david2(~david2@212-186-25-215.cable.dynamic.surfer.at)
2021-03-04 09:24:43 +0100notis(~notis@185.51.134.230)
2021-03-04 09:29:54 +0100batdog_(~batdog@lnsq.elkins.co)
2021-03-04 09:30:00 +0100typetetris_(sid275937@gateway/web/irccloud.com/x-slhwzzrziatkashc)
2021-03-04 09:30:04 +0100belst_(~belst@unaffiliated/belst)
2021-03-04 09:30:29 +0100burp_(~quassel@2001:41d0:2:a512::1)
2021-03-04 09:32:10 +0100tomjagua1paw(~tom@li367-225.members.linode.com)
2021-03-04 09:32:12 +0100funaali_(~funaali@2a01:4f8:1c1c:2605::1)
2021-03-04 09:32:15 +0100ixian8(~mgold@terra.bitplane.org)
2021-03-04 09:32:17 +0100jusa__(~jusa@2a04:3540:1000:310:2462:fcff:febb:ba8)
2021-03-04 09:32:37 +0100weechat3(~mingc@2400:8902::f03c:91ff:feb7:8e82)
2021-03-04 09:33:01 +0100Liskni_s1(~liskin@ackle.nomi.cz)
2021-03-04 09:33:52 +0100dexter(dexter@2a01:7e00::f03c:91ff:fe86:59ec)
2021-03-04 09:40:22 +0100mc47(~yecinem@89.246.239.190)
2021-03-04 09:43:31 +0100belst(~belst@unaffiliated/belst) (*.net *.split)
2021-03-04 09:43:31 +0100burp(~quassel@2001:41d0:2:a512::1) (*.net *.split)
2021-03-04 09:43:31 +0100jusa_(~jusa@2a04:3540:1000:310:2462:fcff:febb:ba8) (*.net *.split)
2021-03-04 09:43:31 +0100dexterfoo(dexter@2a01:7e00::f03c:91ff:fe86:59ec) (*.net *.split)
2021-03-04 09:43:31 +0100batdog(batdog@lnsq.elkins.co) (*.net *.split)
2021-03-04 09:43:31 +0100typetetris(sid275937@gateway/web/irccloud.com/x-stkqjtnjlxzqnxsl) (*.net *.split)
2021-03-04 09:43:31 +0100ixian(~mgold@terra.bitplane.org) (*.net *.split)
2021-03-04 09:43:31 +0100funaali(~funaali@2a01:4f8:1c1c:2605::1) (*.net *.split)
2021-03-04 09:43:31 +0100Liskni_si(~liskin@ackle.nomi.cz) (*.net *.split)
2021-03-04 09:43:31 +0100weechat_1(~mingc@2400:8902::f03c:91ff:feb7:8e82) (*.net *.split)
2021-03-04 09:43:31 +0100tomjaguarpaw(~tom@li367-225.members.linode.com) (*.net *.split)
2021-03-04 09:43:45 +0100typetetris_typetetris
2021-03-04 10:05:17 +0100 <mc47> I'm confused with how XMonad.Actions.CopyWindow works on multiple screens
2021-03-04 10:05:52 +0100 <mc47> when running windows copyToAll, I expected to also find a copy of the window on my second screen
2021-03-04 10:06:46 +0100 <mc47> BUT, it's not there. It's only there when I focus the second screen, and it disappears from the first
2021-03-04 10:06:55 +0100 <mc47> is this an X11 thing?
2021-03-04 10:53:19 +0100 <Liskni_s1> It's an X11 thing
2021-03-04 10:53:53 +0100 <Liskni_s1> It's also XMonad.Operations.windows thing
2021-03-04 10:54:32 +0100 <mc47> because the code in XMonad.Actions.CopyWindow looked pretty harmless
2021-03-04 10:54:46 +0100 <mc47> floating windows also just don't work in multi screens with that
2021-03-04 10:55:56 +0100 <mc47> once I do copy to all, they're always on the unfocused screen
2021-03-04 10:55:56 +0100 <Liskni_s1> In X11 every window has just one position.
2021-03-04 10:56:36 +0100 <Liskni_s1> You'd need to somehow tell the compositor to draw the window elsewhere as well
2021-03-04 10:56:58 +0100 <Liskni_s1> And then you'd need to do something with inputs as well
2021-03-04 10:57:17 +0100 <Liskni_s1> IOW only possible in the Wayland architecture
2021-03-04 10:57:31 +0100 <Liskni_s1> (Or with some sort of hack.)
2021-03-04 10:57:43 +0100Liskni_s1Liskni_si
2021-03-04 10:59:44 +0100 <Solid> 22:27 <Liskni_si> actually in that call for help issue in xmonad, someone suggested that we simply merge everything regardless of quality and give more contributors push rights << I mean, it's not like the bar to get a new module into -contrib is particularly high
2021-03-04 10:59:56 +0100 <Solid> setting it even lower might result in chaos
2021-03-04 11:01:41 +0100 <mc47> I see, thanks for the explanation
2021-03-04 11:02:09 +0100 <mc47> I guess it makes sense to have a sticky windows module
2021-03-04 11:02:25 +0100 <mc47> as in screen specific
2021-03-04 11:05:01 +0100 <Solid> does anyone know why X.U.XSelection.getSelection opens its own connection to the X server instead or re-using xmonad's?
2021-03-04 11:05:23 +0100 <Solid> is it just for the MonadIO constraint?
2021-03-04 11:05:28 +0100 <Solid> This seems to me like a weird priority
2021-03-04 11:12:49 +0100 <Liskni_si> Solid: I don't think the bar is very low actually
2021-03-04 11:14:08 +0100 <Liskni_si> Solid: yeah, I'm not forcing people to do kernel-style perfect commit messages, but I don't merge stuff without proper documentation and we even comment on coding style and so on
2021-03-04 11:14:48 +0100 <Liskni_si> (and yeah, some of this could be automated, which would then spare some reviewer time, probably, but it'd need to clean up the existing pieces first)
2021-03-04 11:14:50 +0100 <Solid> I suppose I have never submitted an entire module (though yesterday I got an idea for a really cool prompt2org module, so I'll probably try to find time for tat)
2021-03-04 11:15:08 +0100 <Liskni_si> re getSelection, did you read through https://code.google.com/archive/p/xmonad/issues/573 ?
2021-03-04 11:15:40 +0100 <Solid> my thinking usually is "if a project wants my garbage code their standards might not be that high" ... :>
2021-03-04 11:15:59 +0100 <mc47> Liskni_si yesterday I ran an hlint check on xmonad-contrib, and there were ~ 1000 warnings
2021-03-04 11:16:25 +0100 <Liskni_si> Solid: that's a thinking that is more dangerous every day you age :-)
2021-03-04 11:16:55 +0100 <mc47> I would go through them (not semi-automatically) if we want to enforce it in the CI
2021-03-04 11:17:30 +0100 <Solid> Liskni_si: I briefly read through that, but it seems to mostly be "how its implemented sucks, but maybe we can salvage it a bit"
2021-03-04 11:17:49 +0100 <Solid> maybe I need to de-mangle that IRC conversation
2021-03-04 11:18:41 +0100 <Liskni_si> yeah it doesn't really answer that question of yours, true :-)
2021-03-04 11:19:30 +0100 <Solid> I want proper primary selection and clipboard integration (in X, without a separate connection) for a proposed module of mine, so I guess I will find out at some point anyways :)
2021-03-04 11:20:24 +0100 <Liskni_si> I guess the real answer will be something like: we need a little event loop just around this one window and we don't want to fiddle with XCheckTypedWindowEvent so let's make another connection
2021-03-04 11:20:27 +0100 <Liskni_si> or something like that
2021-03-04 11:22:23 +0100 <Liskni_si> mc47: I have no opinion about hlint right now, but I guess it probably can't make things worse, so probably why not
2021-03-04 11:23:01 +0100 <Liskni_si> the best way to approach that would probably be to first fix ghc warnings, then maybe hlint warnings
2021-03-04 11:23:37 +0100 <Liskni_si> and this is the kind of thing where just pushing to master without going through PRs might be best :-)
2021-03-04 11:24:23 +0100 <Liskni_si> like do a couple fixes every day, see if CI passes, push to master, rinse, repeat
2021-03-04 11:24:33 +0100 <Solid> you mean people would bikeshed which hlint warnings are "worth" fixing? :)
2021-03-04 11:27:02 +0100 <Liskni_si> that's not my main concern, it's just that once we agree that those warnings should be fixed, there isn't much left to discuss, so there's no point in wasting other people's time on reviewing these changes in a PR
2021-03-04 11:28:44 +0100 <Solid> I see
2021-03-04 11:41:41 +0100thc202(~thc202@unaffiliated/thc202)
2021-03-04 12:00:50 +0100 <mc47> sounds reasonable
2021-03-04 13:00:14 +0100xaltsc(~xaltsc@unaffiliated/xaltsc)
2021-03-04 14:07:36 +0100geekosaur(82650c7a@130.101.12.122)
2021-03-04 14:35:43 +0100geekosaur(82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
2021-03-04 14:51:12 +0100geekosaur(82650c7a@130.101.12.122)
2021-03-04 14:51:46 +0100david2(~david2@212-186-25-215.cable.dynamic.surfer.at) (Quit: WeeChat 3.0.1)
2021-03-04 15:01:08 +0100seschwar(~seschwar@unaffiliated/seschwar)
2021-03-04 15:19:32 +0100kelnoky(~shao@ip1f1285ec.dynamic.kabel-deutschland.de)
2021-03-04 15:41:36 +0100geekosaur(82650c7a@130.101.12.122) (Quit: Connection closed)
2021-03-04 16:04:48 +0100crab(~crab@pitta.toroid.org) (Remote host closed the connection)
2021-03-04 16:06:03 +0100crab(~crab@pitta.toroid.org)
2021-03-04 16:38:11 +0100kw(d4662d5d@212.102.45.93)
2021-03-04 16:39:00 +0100kw(d4662d5d@212.102.45.93) (Client Quit)
2021-03-04 17:29:29 +0100materiyolo(~materiyol@112.204.160.151) (Quit: WeeChat 3.0.1)
2021-03-04 17:39:05 +0100cfricke(~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.0.1)
2021-03-04 18:02:13 +0100geekosaur(82650c7a@130.101.12.122)
2021-03-04 18:06:45 +0100 <Solid> mh I have to say I do like the look of the new website a bit more every time I visit it
2021-03-04 18:07:02 +0100 <Solid> it even works pretty well in eww, bar the huge picture on the front-page
2021-03-04 18:15:56 +0100 <heck-to-the-gnom> mc47: What's the benefit of using your StatusBar vs the older DynamicLog?
2021-03-04 18:16:06 +0100toniz4(~toniz4@unaffiliated/toniz4)
2021-03-04 18:16:31 +0100 <Solid> extensibility
2021-03-04 18:16:45 +0100 <heck-to-the-gnom> At first I thought it just a name change, but then I looked at your commits some more, and found them to be a bit different
2021-03-04 18:16:46 +0100 <Solid> and composability (supposedly, I haven't actually looked at the pr in quite a while :P)
2021-03-04 18:17:03 +0100 <heck-to-the-gnom> composability being? The ease of spinning up a new one?
2021-03-04 18:17:13 +0100 <Solid> plus safety if you count the new porperty-based logging solution
2021-03-04 18:17:23 +0100 <heck-to-the-gnom> (a new PP interface)
2021-03-04 18:17:27 +0100 <Solid> yes, much easier to configure several bars on several monitors without a lot of manual plumbing
2021-03-04 18:18:36 +0100 <heck-to-the-gnom> lets say I had one of these: `dynamicLogWithPP . namedScratchpadFilterOutWorkspacePP $ xmobarPP` - how easy would it be to transfer one of these to the new version once/if it gets accepted?
2021-03-04 18:18:51 +0100 <heck-to-the-gnom> Would it just work as-is?
2021-03-04 18:18:58 +0100 <Solid> yes
2021-03-04 18:19:08 +0100 <Solid> these functions stil exist
2021-03-04 18:19:28 +0100 <Solid> we do obviously provide backwards compatibility; don't want to break every config on the planet ;)
2021-03-04 18:19:50 +0100 <heck-to-the-gnom> No, I mean if I were to replace `dynamicLogWithPP` with the new `StatusBar`?
2021-03-04 18:20:07 +0100 <heck-to-the-gnom> Of course you'd leave the old one for compatibility sake
2021-03-04 18:22:29 +0100 <Solid> I think you'd just use `dynamicLogWithPP'
2021-03-04 18:23:08 +0100 <Solid> actually
2021-03-04 18:23:10 +0100 <Solid> no
2021-03-04 18:23:32 +0100 <Solid> heck-to-the-gnom: you are spawning your status bar manually right?
2021-03-04 18:24:01 +0100 <Solid> then you'd want to use something like statusBarProp
2021-03-04 18:24:12 +0100 <Solid> and remove things like the `docs' combinator
2021-03-04 18:27:17 +0100ADG1089__(~aditya@122.163.141.18)
2021-03-04 18:36:25 +0100 <mc47> heck-to-the-gnom it's more composable, and safer
2021-03-04 18:37:07 +0100 <mc47> basically, if you use it, you can easily have dynamic status bars (that react to screen changes)
2021-03-04 18:37:53 +0100 <mc47> Now, there's no support for multiple status bars: if you want to have more than one status bar, you'd have to write everything by hand
2021-03-04 18:39:58 +0100 <mc47> And to change something like `dynamicLogWithPP . namedScratchpadFilterOutWorkspacePP $ xmobarPP`, you'd have something like `main = do {mySb <- statusBarPipe "xmobar" (namedScratchpadFilterOutWorkspacePP xmobarPP); xmonad =<< makeStatusBar mySb myConf`
2021-03-04 18:41:30 +0100 <Solid> could probably just use `statusBar', no?
2021-03-04 18:41:56 +0100 <mc47> you can get rid of the `do ...` if you use dynamicSBs from #463, and you'd use it like you'd use ewmh or docks
2021-03-04 18:42:47 +0100 <mc47> Solid I removed statusBar' in my PR
2021-03-04 18:43:20 +0100 <mc47> Only the things from the release are kept, the rest is re-implemented in terms of StatusBarConfig
2021-03-04 18:43:35 +0100 <mc47> oh I left xmobarProp, thought it's useful
2021-03-04 18:44:54 +0100 <Solid> huh okay
2021-03-04 18:45:15 +0100 <Solid> seemed like a useful function to keep
2021-03-04 18:45:22 +0100 <Solid> but I was referring the the "normal" statusBar anyways :)
2021-03-04 18:51:36 +0100 <mc47> oh the normal is there
2021-03-04 18:51:45 +0100 <mc47> but it only takes a PP
2021-03-04 18:52:22 +0100 <mc47> btw, even the IORef trick doesn't fix the status bar getting launched too early
2021-03-04 18:53:31 +0100feepo(sid28508@gateway/web/irccloud.com/x-wcewznnvlbknipja) (Ping timeout: 272 seconds)
2021-03-04 18:53:45 +0100tomjagua1pawtomjaguarpaw
2021-03-04 18:54:35 +0100 <Solid> rip
2021-03-04 18:55:03 +0100 <Solid> and what do you mean it only takes a PP?
2021-03-04 18:55:10 +0100ADG1089__(~aditya@122.163.141.18) (Remote host closed the connection)
2021-03-04 18:55:16 +0100 <Solid> It's in 0.16 so surely it takes the arguments it did there?
2021-03-04 18:55:38 +0100feepo(sid28508@gateway/web/irccloud.com/x-gkqhrcmhiiphbogr)
2021-03-04 19:06:11 +0100 <mc47> I mean not X PP
2021-03-04 19:06:53 +0100 <mc47> can get kinda awkward with the binds if someone is trying to follow a config or try it on their own
2021-03-04 19:07:18 +0100 <mc47> the new functions always take X PP to make the interface friendlier
2021-03-04 19:09:09 +0100 <Solid> is =<< so unfriendly? :o
2021-03-04 19:13:08 +0100 <mc47> well no, but PP is the second parameter of statusBar which takes 4 parameters in total, so....
2021-03-04 19:15:22 +0100 <Solid> but none of those parameters is stuck in a MonadIO or similar
2021-03-04 19:15:37 +0100 <Solid> and usually the PP you supply to it is pure anyways
2021-03-04 19:15:56 +0100 <Solid> so you can just do `xmonad =<< statusBar "bar" def tsKey def', no?
2021-03-04 19:16:02 +0100 <Solid> I think I'm missing something
2021-03-04 19:16:41 +0100 <Solid> afaik if you're just using `dynamicLogWithPP' this is exactly the setup you need
2021-03-04 19:18:53 +0100 <mc47> Yeah you could do that, I'm talking if you want to use an X PP instead
2021-03-04 19:19:15 +0100 <mc47> but you're point holds, you can just use statusBar if you don't need any fancy things
2021-03-04 19:19:18 +0100 <fizzie> @pl \x -> statusBar a x b c
2021-03-04 19:19:19 +0100 <lambdabot> flip (flip (statusBar a) b) c
2021-03-04 19:19:52 +0100 <fizzie> There's no problem in the world that couldn't be solved by an unreadable combination of `.`s and `flip`s.
2021-03-04 19:19:52 +0100 <mc47> good bot :)
2021-03-04 19:19:56 +0100 <Solid> it's beautiful
2021-03-04 19:20:07 +0100 <Solid> I like that it's @pl and not @pf
2021-03-04 19:20:09 +0100 <Solid> that's a nice touch
2021-03-04 19:20:43 +0100 <mc47> Well, I guess there's a reason why xmonad users that are non-haskellers don't use statusBar
2021-03-04 19:20:54 +0100 <mc47> or at least I've never seen it used by them
2021-03-04 19:21:18 +0100 <Solid> they don't use it because it's not in the 10 year old examples on the wiki
2021-03-04 19:21:31 +0100 <Solid> nor in that dude-from-youtube's config
2021-03-04 19:22:01 +0100 <mc47> that config is basically the start point of many new users
2021-03-04 19:22:16 +0100 <mc47> yeah, whoever updated the docs between the release and now did a great job
2021-03-04 19:22:22 +0100 <Solid> I always advise them to use it and usually there are absolutely no troubles with getting that to work (if someone needs an `X PP' they're probably an advanced user anyways)
2021-03-04 19:22:31 +0100 <mc47> true
2021-03-04 19:22:33 +0100 <Solid> (I did)
2021-03-04 19:22:37 +0100 <Solid> :D
2021-03-04 19:23:00 +0100 <mc47> well kudos!
2021-03-04 19:23:04 +0100 <Solid> <3
2021-03-04 19:31:08 +0100 <heck-to-the-gnom> Yeah, my config originally started from DT's (the guy on youtube). But I've modified it so much, its barely recognizable.
2021-03-04 19:31:42 +0100 <Liskni_si> mc47: what's with the IORef trick?
2021-03-04 19:32:10 +0100 <mc47> The one you mentioned
2021-03-04 19:32:21 +0100 <mc47> delaying the spawning to the startupHook
2021-03-04 19:32:56 +0100 <Liskni_si> so what's wrong with it?
2021-03-04 19:33:27 +0100 <mc47> (sorry, too much time on the screen I can barely read things correctly)
2021-03-04 19:33:44 +0100 <mc47> that "race condition" still occurs somehow
2021-03-04 19:34:09 +0100 <mc47> either the bars don't get spawned at all, the they get spawned with a broken pipe (Updating ...)
2021-03-04 19:34:25 +0100 <heck-to-the-gnom> I've been configuring it for almost 6 months, and it's been usable for about 5, but it's an ongoing process. I think I'm getting close to my config remaining static. After that I'll replicate my config in the `penrose WM` just for the heck of it, and I'd like to learn rust at some point, so...
2021-03-04 19:34:51 +0100 <heck-to-the-gnom> Does this race condition just exist with statusbar? Or with dynamiclog too?
2021-03-04 19:35:07 +0100 <heck-to-the-gnom> I've never had any issues with dynamic log, well, nothing like that.
2021-03-04 19:35:49 +0100 <Liskni_si> mc47: that makes little sense :-/
2021-03-04 19:36:23 +0100 <Liskni_si> I'd need to see the code I guess
2021-03-04 19:38:10 +0100 <heck-to-the-gnom> I get the `Updating...` thing, but only when I try to place `\x000` style escape codes in my xmobar config, and also only when on pure arch. Manjaro does something differently. And the nix install makes 0 difference.
2021-03-04 19:38:10 +0100 <heck-to-the-gnom> I've temporarily replaced my `mononoki nerd font` characters that I was using with letters.
2021-03-04 19:39:27 +0100 <mc47> Liskni_si I know, but that's what's happening :/ here's my config for reference https://github.com/TheMC47/dotfiles/blob/master/.xmonad/src/Config.hs
2021-03-04 19:40:09 +0100 <mc47> stack at #463
2021-03-04 19:41:22 +0100 <mc47> heck-to-the-gnom if you start your status bar manually you won't encounter the problem
2021-03-04 19:41:34 +0100 <mc47> but that method has a lot of boilerplate, among other problems
2021-03-04 19:43:36 +0100 <Liskni_si> mc47: where shall I look for the IORef?
2021-03-04 19:46:01 +0100 <mc47> nevermind... turns out I forgot to add it
2021-03-04 19:46:31 +0100 <mc47> that's embarrassing hahaha
2021-03-04 19:46:52 +0100 <Liskni_si> :-)
2021-03-04 19:46:59 +0100 <Liskni_si> now it does make sense :-D
2021-03-04 19:47:06 +0100 <mc47> totally lol
2021-03-04 19:49:58 +0100 <Solid> lol
2021-03-04 19:52:02 +0100growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net)
2021-03-04 19:53:05 +0100 <Solid> man, I can't wait to return to hacking on things
2021-03-04 19:53:43 +0100geekosaur(82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
2021-03-04 20:13:19 +0100geekosaur(82650c7a@130.101.12.122)
2021-03-04 20:20:03 +0100 <heck-to-the-gnom> Solid: Why can't/aren't you?
2021-03-04 20:21:24 +0100 <geekosaur> thesis, I think
2021-03-04 20:22:20 +0100 <heck-to-the-gnom> Ah
2021-03-04 20:23:07 +0100 <heck-to-the-gnom> Much more disciplined than me. I'm just scatterbrained, I have trouble staying on the same task, well, unless it's fun. I should probably get some AD(H)D medicine tbh.
2021-03-04 20:27:53 +0100 <heck-to-the-gnom> mc47: Does your config have an example of starting it manually? My log (workspaces, window name -- the unsafeSTDReader) works, it's just when in my XMobar.conf (yeah, yeah, I'll move it to a .hs sometime) has `Run Com "echo" ["\xfidk"] 0`, those remain on "Updating..."
2021-03-04 20:28:20 +0100 <mc47> what do you mean?
2021-03-04 20:28:40 +0100 <heck-to-the-gnom> here, I'll get a screenshot
2021-03-04 20:30:10 +0100heck-to-the-gnomuploaded an image: image.png (209KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/LlRaKFZlWZUydKxgdNiCcDvg/image.png >
2021-03-04 20:31:27 +0100 <heck-to-the-gnom> See where it says "Updating..."? That's where my vim cursor is in my xmobar conf.
2021-03-04 20:32:03 +0100 <mc47> and what are you expecting?
2021-03-04 20:32:16 +0100 <mc47> Can you show me your xmonad config?
2021-03-04 20:35:30 +0100Ikosit(vherrmanns@gateway/shell/matrix.org/x-hmvzdbbomixuiazx)
2021-03-04 20:35:33 +0100 <heck-to-the-gnom> Sure, it's a leviathan for a WM, but for the time being it's hosted at https://github.com/techtiger255/xbronad
2021-03-04 20:36:00 +0100 <heck-to-the-gnom> This one's a bit stale, but I haven't touched my xmobar stuff much since then
2021-03-04 20:39:41 +0100Nahra(~Nahra@unaffiliated/nahra)
2021-03-04 20:43:13 +0100 <heck-to-the-gnom> Oh, sorry, realized I left a question of yours unanswered, see the volume icon, and the power icon? Near the top right? It's supposed to look like that, but when I run it through echo on arch (instead of manjaro) it doesn't ever resolve
2021-03-04 20:43:54 +0100 <heck-to-the-gnom> It works if I use a different command, as you can see.
2021-03-04 20:44:02 +0100 <geekosaur> echo may only be provided as a shell built-in there? the standalone one's pretty silly
2021-03-04 20:50:01 +0100rafadc(~rafadc@213.37.16.152.dyn.user.ono.com)
2021-03-04 20:55:54 +0100 <mc47> heck-to-the-gnom I thought you were asking me about the new interface
2021-03-04 21:12:39 +0100 <heck-to-the-gnom> I was, but I was asking if it would solve this problem, but it does seem a bit out of scope.
2021-03-04 21:17:30 +0100 <heck-to-the-gnom> geekosaur: it's whatever my shell determines (`~/.nix-profile/bin/echo`), with a fallback of `/bin/echo`
2021-03-04 21:17:32 +0100 <mc47> No, that's just xmobar
2021-03-04 21:17:47 +0100 <heck-to-the-gnom> OK, good to know.
2021-03-04 21:18:29 +0100 <mc47> (or something else related to that, no idea though)
2021-03-04 21:18:43 +0100 <heck-to-the-gnom> geekosaur: If it helps at all: replacing "echo" with "/bin/echo" or my nix one, it makes no difference
2021-03-04 21:18:56 +0100 <heck-to-the-gnom> I tried both the cabal and stack versions, same result
2021-03-04 21:51:25 +0100xsperry(~as@unaffiliated/xsperry)
2021-03-04 22:07:47 +0100adamik(~nodelet@unaffiliated/adamik)
2021-03-04 22:13:52 +0100jd_(~jd@23-127-25-87.lightspeed.rcsntx.sbcglobal.net)
2021-03-04 22:13:55 +0100jd_juliusdelta
2021-03-04 22:14:25 +0100 <juliusdelta> Whenever I update xmonad, it breaks after a reboot. I have to login as my root user and I typically reinstall and recompile it for my main user. Anyone else encounter this before?
2021-03-04 22:15:04 +0100 <juliusdelta> should I recompile it before rebooting after updates?
2021-03-04 22:21:53 +0100 <heck-to-the-gnom> Probably, it depends on how big the update was, if it was only bug squashing, semantic changes, or performance boosts, then you shouldn't have to recompile. But, if Xmonad updates, and it breaks or changes something you were using, then it might not accept the binary. I personally haven't experienced this, but that's my guess.
2021-03-04 22:22:21 +0100 <juliusdelta> Welp Arch Wiki to the rescue. -> "Remember to run xmonad --recompile after you upgrade xmonad..."
2021-03-04 22:23:32 +0100 <juliusdelta> Yeah the xsession-error seems like the binary it's looking for doesn't line up
2021-03-04 22:24:09 +0100 <heck-to-the-gnom> Oof! A wise man once told me to never use the arch install of xmonad. I'm on arch, BUT, I use the nix install. (https://nixos.org/nix)
2021-03-04 22:25:22 +0100 <juliusdelta> Oh interesting. I'm on arch and use the arch install lol. I haven't had any problems but this one. The wiki also has a useful pacman hook to auto recompile after updates
2021-03-04 22:25:29 +0100 <juliusdelta> https://wiki.archlinux.org/index.php/Xmonad#Problems_with_finding_shared_libraries_after_update
2021-03-04 22:26:36 +0100 <Liskni_si> The wise man probably had this one in mind.
2021-03-04 22:26:56 +0100thc202(~thc202@unaffiliated/thc202) (Ping timeout: 240 seconds)
2021-03-04 22:26:58 +0100 <geekosaur> one problem is you otherwise need a build script to inject -dynamic, because arch
2021-03-04 22:27:44 +0100 <Liskni_si> (Although I do wonder how wise men acquire pacman experience, as wise men should know better than to use pacman.)
2021-03-04 22:28:55 +0100 <heck-to-the-gnom> Pacman is a second to nix/nix derivitives imo (being guix's package manager, and I'm certain there's others out there)
2021-03-04 22:29:06 +0100 <heck-to-the-gnom> But I do prefer to use nix wherever possible
2021-03-04 22:29:50 +0100 <heck-to-the-gnom> I just take issue with the software availability aspect of nix, seeing as I'm too inexperienced with it. But, as I get more and more comfortable with these tools, I may try nixOS some day.
2021-03-04 22:30:55 +0100 <heck-to-the-gnom> juliusdelta: Yeah, I ran into a HUUGE issue when I tried to install another library from cabal. The thing wouldn't compile, it's because arch forces dynamically linked libraries? Or static, bah, I can't remember. Anyway, point is, if you ever want to install any library that's not used in the creation of xmonad, xmonad-contrib, or a submodule of XMonad, then it'll fail for you. I tried to install the `random-fu`
2021-03-04 22:30:55 +0100 <heck-to-the-gnom> package, with `Data.List.`something, I forget exactly, its been almost 5 months now. I kind of purged the minor details of that experience from my mind.
2021-03-04 22:33:59 +0100 <geekosaur> haskell defaults to static, arch removes all the static libraries and forces you to use -dynamic
2021-03-04 22:34:01 +0100 <juliusdelta> Yeah generally I've heard Arch + Haskell in general is pretty awful. Thankfully the only Haskell I need is for Xmonad.
2021-03-04 22:38:25 +0100 <heck-to-the-gnom> I just discovered that pandoc is haskell too... If you use that.
2021-03-04 22:40:31 +0100 <heck-to-the-gnom> But alas, it's a simple thing to fix, just install it via the nix package manager, once you have it, just well, actually, it's a bit more complicated than this (if you want as much support as possible), but simplified: `nix-env -iA nixpkgs.haskellPackages.xmonad nixpkgs.haskellPackages.xmonad-contrib`
2021-03-04 22:41:33 +0100geekosaur(82650c7a@130.101.12.122) (Quit: Connection closed)
2021-03-04 22:42:19 +0100mc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-03-04 22:49:47 +0100 <Liskni_si> I honestly don't understand why Arch is the only distro that uses -dynamic with Haskell.
2021-03-04 22:50:15 +0100 <Liskni_si> If anything, I'd expect the exact opposite. All the other distros with proper package managers could actually do that safely, and Arch would be the only one that can't, so it wouldn't.
2021-03-04 22:50:28 +0100 <Liskni_si> But of course it's the other way round, because this world is just bonkers.
2021-03-04 22:51:37 +0100 <Liskni_si> (And by proper I mean the ability to say "if this gets upgraded, that needs to be upgraded too, so either do that or refuse the transaction")
2021-03-04 22:54:08 +0100Nahra(~Nahra@unaffiliated/nahra) (Quit: leaving)
2021-03-04 23:10:15 +0100evanjs(~evanjs@075-129-098-007.res.spectrum.com) (Read error: Connection reset by peer)
2021-03-04 23:10:46 +0100evanjs(~evanjs@075-129-098-007.res.spectrum.com)
2021-03-04 23:27:48 +0100juliusdelta(~jd@23-127-25-87.lightspeed.rcsntx.sbcglobal.net) (Quit: leaving)