Home freenode/#xmonad: Logs Calendar

Logs on 2021-03-04 (freenode/#xmonad)

00:03:45 <vrs> it used to be when I ran it, which was 2014-ish
00:14:31 × evanjs quits (~evanjs@075-129-098-007.res.spectrum.com) (Read error: Connection reset by peer)
00:16:59 evanjs joins (~evanjs@075-129-098-007.res.spectrum.com)
00:34:38 × notis quits (~notis@185.51.134.230) (Read error: Connection reset by peer)
00:40:00 × toniz4 quits (~toniz4@unaffiliated/toniz4) (Quit: bye)
00:53:55 st13g_ is now known as st13g
01:08:49 <Steven_M> vrs: oh, I can't find the port for it.
01:10:46 <vrs> they apparently removed it? https://www.freshports.org/x11-wm/hs-xmonad-contrib
01:10:57 <vrs> I don't quite understand why
01:12:02 <vrs> https://forums.freebsd.org/threads/what-happened-to-xmonad-contrib-and-some-other-gripes.77203/
01:12:44 <vrs> I don't know if cabal or stack is currently the recommended way?
01:17:04 <Steven_M> okay, thanks for the info. :)
01:17:52 <Steven_M> vrs: see above
01:18:10 <vrs> saw
01:47:06 × adamik quits (~nodelet@unaffiliated/adamik) (Quit: leaving)
02:21:53 def_jam is now known as eblip
02:33:29 × pharaun quits (~pharaun@static.88-198-62-245.clients.your-server.de) (Ping timeout: 256 seconds)
02:44:12 pharaun joins (~pharaun@static.88-198-62-245.clients.your-server.de)
02:53:14 × Steven_M quits (~Steven_M@unaffiliated/steven-m/x-3557666) (Quit: busy)
03:43:21 × theDon quits (~td@muedsl-82-207-238-151.citykom.de) (Ping timeout: 246 seconds)
03:45:17 theDon joins (~td@94.134.91.49)
04:04:04 × dxld quits (~dxld@rush.pub.dxld.at) (Ping timeout: 240 seconds)
04:05:50 dxld joins (~dxld@80-109-136-248.cable.dynamic.surfer.at)
04:59:03 materiyolo joins (~materiyol@112.204.160.151)
06:11:04 palo1 joins (~weechat@c-base/crew/palo)
06:14:29 × palo quits (~weechat@c-base/crew/palo) (Ping timeout: 256 seconds)
06:14:29 palo1 is now known as palo
06:19:50 × growpotkin quits (~growpotki@130-45-30-154.dyn.grandenetworks.net) (Quit: ZNC 1.8.2 - https://znc.in)
07:10:28 cfricke joins (~cfricke@unaffiliated/cfricke)
08:20:38 david2 joins (~david2@212-186-25-215.cable.dynamic.surfer.at)
08:24:43 notis joins (~notis@185.51.134.230)
08:29:54 batdog_ joins (~batdog@lnsq.elkins.co)
08:30:00 typetetris_ joins (sid275937@gateway/web/irccloud.com/x-slhwzzrziatkashc)
08:30:04 belst_ joins (~belst@unaffiliated/belst)
08:30:29 burp_ joins (~quassel@2001:41d0:2:a512::1)
08:32:10 tomjagua1paw joins (~tom@li367-225.members.linode.com)
08:32:12 funaali_ joins (~funaali@2a01:4f8:1c1c:2605::1)
08:32:15 ixian8 joins (~mgold@terra.bitplane.org)
08:32:17 jusa__ joins (~jusa@2a04:3540:1000:310:2462:fcff:febb:ba8)
08:32:37 weechat3 joins (~mingc@2400:8902::f03c:91ff:feb7:8e82)
08:33:01 Liskni_s1 joins (~liskin@ackle.nomi.cz)
08:33:52 dexter joins (dexter@2a01:7e00::f03c:91ff:fe86:59ec)
08:40:22 mc47 joins (~yecinem@89.246.239.190)
08:43:31 × belst quits (~belst@unaffiliated/belst) (*.net *.split)
08:43:31 × burp quits (~quassel@2001:41d0:2:a512::1) (*.net *.split)
08:43:31 × jusa_ quits (~jusa@2a04:3540:1000:310:2462:fcff:febb:ba8) (*.net *.split)
08:43:31 × dexterfoo quits (dexter@2a01:7e00::f03c:91ff:fe86:59ec) (*.net *.split)
08:43:31 × batdog quits (batdog@lnsq.elkins.co) (*.net *.split)
08:43:31 × typetetris quits (sid275937@gateway/web/irccloud.com/x-stkqjtnjlxzqnxsl) (*.net *.split)
08:43:31 × ixian quits (~mgold@terra.bitplane.org) (*.net *.split)
08:43:31 × funaali quits (~funaali@2a01:4f8:1c1c:2605::1) (*.net *.split)
08:43:31 × Liskni_si quits (~liskin@ackle.nomi.cz) (*.net *.split)
08:43:31 × weechat_1 quits (~mingc@2400:8902::f03c:91ff:feb7:8e82) (*.net *.split)
08:43:31 × tomjaguarpaw quits (~tom@li367-225.members.linode.com) (*.net *.split)
08:43:45 typetetris_ is now known as typetetris
09:05:17 <mc47> I'm confused with how XMonad.Actions.CopyWindow works on multiple screens
09:05:52 <mc47> when running windows copyToAll, I expected to also find a copy of the window on my second screen
09:06:46 <mc47> BUT, it's not there. It's only there when I focus the second screen, and it disappears from the first
09:06:55 <mc47> is this an X11 thing?
09:53:19 <Liskni_s1> It's an X11 thing
09:53:53 <Liskni_s1> It's also XMonad.Operations.windows thing
09:54:32 <mc47> because the code in XMonad.Actions.CopyWindow looked pretty harmless
09:54:46 <mc47> floating windows also just don't work in multi screens with that
09:55:56 <mc47> once I do copy to all, they're always on the unfocused screen
09:55:56 <Liskni_s1> In X11 every window has just one position.
09:56:36 <Liskni_s1> You'd need to somehow tell the compositor to draw the window elsewhere as well
09:56:58 <Liskni_s1> And then you'd need to do something with inputs as well
09:57:17 <Liskni_s1> IOW only possible in the Wayland architecture
09:57:31 <Liskni_s1> (Or with some sort of hack.)
09:57:43 Liskni_s1 is now known as Liskni_si
09:59:44 <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
09:59:56 <Solid> setting it even lower might result in chaos
10:01:41 <mc47> I see, thanks for the explanation
10:02:09 <mc47> I guess it makes sense to have a sticky windows module
10:02:25 <mc47> as in screen specific
10:05:01 <Solid> does anyone know why X.U.XSelection.getSelection opens its own connection to the X server instead or re-using xmonad's?
10:05:23 <Solid> is it just for the MonadIO constraint?
10:05:28 <Solid> This seems to me like a weird priority
10:12:49 <Liskni_si> Solid: I don't think the bar is very low actually
10:14:08 <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
10:14:48 <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)
10:14:50 <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)
10:15:08 <Liskni_si> re getSelection, did you read through https://code.google.com/archive/p/xmonad/issues/573 ?
10:15:40 <Solid> my thinking usually is "if a project wants my garbage code their standards might not be that high" ... :>
10:15:59 <mc47> Liskni_si yesterday I ran an hlint check on xmonad-contrib, and there were ~ 1000 warnings
10:16:25 <Liskni_si> Solid: that's a thinking that is more dangerous every day you age :-)
10:16:55 <mc47> I would go through them (not semi-automatically) if we want to enforce it in the CI
10:17:30 <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"
10:17:49 <Solid> maybe I need to de-mangle that IRC conversation
10:18:41 <Liskni_si> yeah it doesn't really answer that question of yours, true :-)
10:19:30 <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 :)
10:20:24 <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
10:20:27 <Liskni_si> or something like that
10:22:23 <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
10:23:01 <Liskni_si> the best way to approach that would probably be to first fix ghc warnings, then maybe hlint warnings
10:23:37 <Liskni_si> and this is the kind of thing where just pushing to master without going through PRs might be best :-)
10:24:23 <Liskni_si> like do a couple fixes every day, see if CI passes, push to master, rinse, repeat
10:24:33 <Solid> you mean people would bikeshed which hlint warnings are "worth" fixing? :)
10:27:02 <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
10:28:44 <Solid> I see
10:41:41 thc202 joins (~thc202@unaffiliated/thc202)
11:00:50 <mc47> sounds reasonable
12:00:14 xaltsc joins (~xaltsc@unaffiliated/xaltsc)
13:07:36 geekosaur joins (82650c7a@130.101.12.122)
13:35:43 × geekosaur quits (82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
13:51:12 geekosaur joins (82650c7a@130.101.12.122)
13:51:46 × david2 quits (~david2@212-186-25-215.cable.dynamic.surfer.at) (Quit: WeeChat 3.0.1)
14:01:08 seschwar joins (~seschwar@unaffiliated/seschwar)
14:19:32 kelnoky joins (~shao@ip1f1285ec.dynamic.kabel-deutschland.de)
14:41:36 × geekosaur quits (82650c7a@130.101.12.122) (Quit: Connection closed)
15:04:48 × crab quits (~crab@pitta.toroid.org) (Remote host closed the connection)
15:06:03 crab joins (~crab@pitta.toroid.org)
15:38:11 kw joins (d4662d5d@212.102.45.93)
15:39:00 × kw quits (d4662d5d@212.102.45.93) (Client Quit)
16:29:29 × materiyolo quits (~materiyol@112.204.160.151) (Quit: WeeChat 3.0.1)
16:39:05 × cfricke quits (~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.0.1)
17:02:13 geekosaur joins (82650c7a@130.101.12.122)
17:06:45 <Solid> mh I have to say I do like the look of the new website a bit more every time I visit it
17:07:02 <Solid> it even works pretty well in eww, bar the huge picture on the front-page
17:15:56 <heck-to-the-gnom> mc47: What's the benefit of using your StatusBar vs the older DynamicLog?
17:16:06 toniz4 joins (~toniz4@unaffiliated/toniz4)
17:16:31 <Solid> extensibility
17:16:45 <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
17:16:46 <Solid> and composability (supposedly, I haven't actually looked at the pr in quite a while :P)
17:17:03 <heck-to-the-gnom> composability being? The ease of spinning up a new one?
17:17:13 <Solid> plus safety if you count the new porperty-based logging solution
17:17:23 <heck-to-the-gnom> (a new PP interface)
17:17:27 <Solid> yes, much easier to configure several bars on several monitors without a lot of manual plumbing
17:18:36 <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?
17:18:51 <heck-to-the-gnom> Would it just work as-is?
17:18:58 <Solid> yes
17:19:08 <Solid> these functions stil exist
17:19:28 <Solid> we do obviously provide backwards compatibility; don't want to break every config on the planet ;)
17:19:50 <heck-to-the-gnom> No, I mean if I were to replace `dynamicLogWithPP` with the new `StatusBar`?
17:20:07 <heck-to-the-gnom> Of course you'd leave the old one for compatibility sake
17:22:29 <Solid> I think you'd just use `dynamicLogWithPP'
17:23:08 <Solid> actually
17:23:10 <Solid> no
17:23:32 <Solid> heck-to-the-gnom: you are spawning your status bar manually right?
17:24:01 <Solid> then you'd want to use something like statusBarProp
17:24:12 <Solid> and remove things like the `docs' combinator
17:27:17 ADG1089__ joins (~aditya@122.163.141.18)
17:36:25 <mc47> heck-to-the-gnom it's more composable, and safer
17:37:07 <mc47> basically, if you use it, you can easily have dynamic status bars (that react to screen changes)
17:37:53 <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
17:39:58 <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`
17:41:30 <Solid> could probably just use `statusBar', no?
17:41:56 <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
17:42:47 <mc47> Solid I removed statusBar' in my PR
17:43:20 <mc47> Only the things from the release are kept, the rest is re-implemented in terms of StatusBarConfig
17:43:35 <mc47> oh I left xmobarProp, thought it's useful
17:44:54 <Solid> huh okay
17:45:15 <Solid> seemed like a useful function to keep
17:45:22 <Solid> but I was referring the the "normal" statusBar anyways :)
17:51:36 <mc47> oh the normal is there
17:51:45 <mc47> but it only takes a PP
17:52:22 <mc47> btw, even the IORef trick doesn't fix the status bar getting launched too early
17:53:31 × feepo quits (sid28508@gateway/web/irccloud.com/x-wcewznnvlbknipja) (Ping timeout: 272 seconds)
17:53:45 tomjagua1paw is now known as tomjaguarpaw
17:54:35 <Solid> rip
17:55:03 <Solid> and what do you mean it only takes a PP?
17:55:10 × ADG1089__ quits (~aditya@122.163.141.18) (Remote host closed the connection)
17:55:16 <Solid> It's in 0.16 so surely it takes the arguments it did there?
17:55:38 feepo joins (sid28508@gateway/web/irccloud.com/x-gkqhrcmhiiphbogr)
18:06:11 <mc47> I mean not X PP
18:06:53 <mc47> can get kinda awkward with the binds if someone is trying to follow a config or try it on their own
18:07:18 <mc47> the new functions always take X PP to make the interface friendlier
18:09:09 <Solid> is =<< so unfriendly? :o
18:13:08 <mc47> well no, but PP is the second parameter of statusBar which takes 4 parameters in total, so....
18:15:22 <Solid> but none of those parameters is stuck in a MonadIO or similar
18:15:37 <Solid> and usually the PP you supply to it is pure anyways
18:15:56 <Solid> so you can just do `xmonad =<< statusBar "bar" def tsKey def', no?
18:16:02 <Solid> I think I'm missing something
18:16:41 <Solid> afaik if you're just using `dynamicLogWithPP' this is exactly the setup you need
18:18:53 <mc47> Yeah you could do that, I'm talking if you want to use an X PP instead
18:19:15 <mc47> but you're point holds, you can just use statusBar if you don't need any fancy things
18:19:18 <fizzie> @pl \x -> statusBar a x b c
18:19:19 <lambdabot> flip (flip (statusBar a) b) c
18:19:52 <fizzie> There's no problem in the world that couldn't be solved by an unreadable combination of `.`s and `flip`s.
18:19:52 <mc47> good bot :)
18:19:56 <Solid> it's beautiful
18:20:07 <Solid> I like that it's @pl and not @pf
18:20:09 <Solid> that's a nice touch
18:20:43 <mc47> Well, I guess there's a reason why xmonad users that are non-haskellers don't use statusBar
18:20:54 <mc47> or at least I've never seen it used by them
18:21:18 <Solid> they don't use it because it's not in the 10 year old examples on the wiki
18:21:31 <Solid> nor in that dude-from-youtube's config
18:22:01 <mc47> that config is basically the start point of many new users
18:22:16 <mc47> yeah, whoever updated the docs between the release and now did a great job
18:22:22 <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)
18:22:31 <mc47> true
18:22:33 <Solid> (I did)
18:22:37 <Solid> :D
18:23:00 <mc47> well kudos!
18:23:04 <Solid> <3
18:31:08 <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.
18:31:42 <Liskni_si> mc47: what's with the IORef trick?
18:32:10 <mc47> The one you mentioned
18:32:21 <mc47> delaying the spawning to the startupHook
18:32:56 <Liskni_si> so what's wrong with it?
18:33:27 <mc47> (sorry, too much time on the screen I can barely read things correctly)
18:33:44 <mc47> that "race condition" still occurs somehow
18:34:09 <mc47> either the bars don't get spawned at all, the they get spawned with a broken pipe (Updating ...)
18:34:25 <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...
18:34:51 <heck-to-the-gnom> Does this race condition just exist with statusbar? Or with dynamiclog too?
18:35:07 <heck-to-the-gnom> I've never had any issues with dynamic log, well, nothing like that.
18:35:49 <Liskni_si> mc47: that makes little sense :-/
18:36:23 <Liskni_si> I'd need to see the code I guess
18:38:10 <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.
18:38:10 <heck-to-the-gnom> I've temporarily replaced my `mononoki nerd font` characters that I was using with letters.
18:39:27 <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
18:40:09 <mc47> stack at #463
18:41:22 <mc47> heck-to-the-gnom if you start your status bar manually you won't encounter the problem
18:41:34 <mc47> but that method has a lot of boilerplate, among other problems
18:43:36 <Liskni_si> mc47: where shall I look for the IORef?
18:46:01 <mc47> nevermind... turns out I forgot to add it
18:46:31 <mc47> that's embarrassing hahaha
18:46:52 <Liskni_si> :-)
18:46:59 <Liskni_si> now it does make sense :-D
18:47:06 <mc47> totally lol
18:49:58 <Solid> lol
18:52:02 growpotkin joins (~growpotki@130-45-30-154.dyn.grandenetworks.net)
18:53:05 <Solid> man, I can't wait to return to hacking on things
18:53:43 × geekosaur quits (82650c7a@130.101.12.122) (Ping timeout: 240 seconds)
19:13:19 geekosaur joins (82650c7a@130.101.12.122)
19:20:03 <heck-to-the-gnom> Solid: Why can't/aren't you?
19:21:24 <geekosaur> thesis, I think
19:22:20 <heck-to-the-gnom> Ah
19:23:07 <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.
19:27:53 <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..."
19:28:20 <mc47> what do you mean?
19:28:40 <heck-to-the-gnom> here, I'll get a screenshot
19:30:10 heck-to-the-gnom uploaded an image: image.png (209KiB) < https://matrix.org/_matrix/media/r0/download/matrix.org/LlRaKFZlWZUydKxgdNiCcDvg/image.png >
19:31:27 <heck-to-the-gnom> See where it says "Updating..."? That's where my vim cursor is in my xmobar conf.
19:32:03 <mc47> and what are you expecting?
19:32:16 <mc47> Can you show me your xmonad config?
19:35:30 Ikosit joins (vherrmanns@gateway/shell/matrix.org/x-hmvzdbbomixuiazx)
19:35:33 <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
19:36:00 <heck-to-the-gnom> This one's a bit stale, but I haven't touched my xmobar stuff much since then
19:39:41 Nahra joins (~Nahra@unaffiliated/nahra)
19:43:13 <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
19:43:54 <heck-to-the-gnom> It works if I use a different command, as you can see.
19:44:02 <geekosaur> echo may only be provided as a shell built-in there? the standalone one's pretty silly
19:50:01 rafadc joins (~rafadc@213.37.16.152.dyn.user.ono.com)
19:55:54 <mc47> heck-to-the-gnom I thought you were asking me about the new interface
20:12:39 <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.
20:17:30 <heck-to-the-gnom> geekosaur: it's whatever my shell determines (`~/.nix-profile/bin/echo`), with a fallback of `/bin/echo`
20:17:32 <mc47> No, that's just xmobar
20:17:47 <heck-to-the-gnom> OK, good to know.
20:18:29 <mc47> (or something else related to that, no idea though)
20:18:43 <heck-to-the-gnom> geekosaur: If it helps at all: replacing "echo" with "/bin/echo" or my nix one, it makes no difference
20:18:56 <heck-to-the-gnom> I tried both the cabal and stack versions, same result
20:51:25 xsperry joins (~as@unaffiliated/xsperry)
21:07:47 adamik joins (~nodelet@unaffiliated/adamik)
21:13:52 jd_ joins (~jd@23-127-25-87.lightspeed.rcsntx.sbcglobal.net)
21:13:55 jd_ is now known as juliusdelta
21:14:25 <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?
21:15:04 <juliusdelta> should I recompile it before rebooting after updates?
21:21:53 <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.
21:22:21 <juliusdelta> Welp Arch Wiki to the rescue. -> "Remember to run xmonad --recompile after you upgrade xmonad..."
21:23:32 <juliusdelta> Yeah the xsession-error seems like the binary it's looking for doesn't line up
21:24:09 <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)
21:25:22 <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
21:25:29 <juliusdelta> https://wiki.archlinux.org/index.php/Xmonad#Problems_with_finding_shared_libraries_after_update
21:26:36 <Liskni_si> The wise man probably had this one in mind.
21:26:56 × thc202 quits (~thc202@unaffiliated/thc202) (Ping timeout: 240 seconds)
21:26:58 <geekosaur> one problem is you otherwise need a build script to inject -dynamic, because arch
21:27:44 <Liskni_si> (Although I do wonder how wise men acquire pacman experience, as wise men should know better than to use pacman.)
21:28:55 <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)
21:29:06 <heck-to-the-gnom> But I do prefer to use nix wherever possible
21:29:50 <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.
21:30:55 <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`
21:30:55 <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.
21:33:59 <geekosaur> haskell defaults to static, arch removes all the static libraries and forces you to use -dynamic
21:34:01 <juliusdelta> Yeah generally I've heard Arch + Haskell in general is pretty awful. Thankfully the only Haskell I need is for Xmonad.
21:38:25 <heck-to-the-gnom> I just discovered that pandoc is haskell too... If you use that.
21:40:31 <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`
21:41:33 × geekosaur quits (82650c7a@130.101.12.122) (Quit: Connection closed)
21:42:19 × mc47 quits (~yecinem@89.246.239.190) (Remote host closed the connection)
21:49:47 <Liskni_si> I honestly don't understand why Arch is the only distro that uses -dynamic with Haskell.
21:50:15 <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.
21:50:28 <Liskni_si> But of course it's the other way round, because this world is just bonkers.
21:51:37 <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")
21:54:08 × Nahra quits (~Nahra@unaffiliated/nahra) (Quit: leaving)
22:10:15 × evanjs quits (~evanjs@075-129-098-007.res.spectrum.com) (Read error: Connection reset by peer)
22:10:46 evanjs joins (~evanjs@075-129-098-007.res.spectrum.com)
22:27:48 × juliusdelta quits (~jd@23-127-25-87.lightspeed.rcsntx.sbcglobal.net) (Quit: leaving)
23:10:55 × vanvik quits (~nimor@82.194.204.210) (Quit: Ping timeout (120 seconds))
23:11:25 vanvik joins (~nimor@82.194.204.210)
23:29:23 × seschwar quits (~seschwar@unaffiliated/seschwar) (Quit: :wq)
23:40:44 materiyolo joins (~materiyol@112.204.160.151)

All times are in UTC on 2021-03-04.