2021/06/02

2021-06-02 00:00:54 +0000tv(~tv@user/tv) (Ping timeout: 264 seconds)
2021-06-02 00:01:19 +0000tv(~tv@user/tv)
2021-06-02 01:02:00 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Ping timeout: 245 seconds)
2021-06-02 01:03:25 +0000jg(~jrgiacone@47.149.222.98)
2021-06-02 01:03:38 +0000 <jg> liskin how di you get around the X11-1.9.2 error
2021-06-02 01:03:42 +0000 <jg> did
2021-06-02 01:03:51 +0000 <jg> when updating to todays update
2021-06-02 01:04:20 +0000 <liskin> jg: if building by stack you'll need to add X11-1.10 to extra-deps
2021-06-02 01:05:59 +0000 <jg> ah lit, thats chill, I was on those lines but did not want to break something :) thanks
2021-06-02 01:06:17 +0000 <jg> how was your day today ?
2021-06-02 01:09:38 +0000 <liskin> quite productive
2021-06-02 01:11:16 +0000 <jg> oh that's great to hear :), so good day overall?
2021-06-02 01:11:29 +0000 <liskin> better than many other, yeah
2021-06-02 01:11:37 +0000 <jg> im glad!
2021-06-02 01:12:19 +0000 <liskin> but I just wasted part of the night trying to understand why Discord keeps ruining power management here
2021-06-02 01:12:33 +0000 <liskin> so I won't get enough sleep for tomorrow :-(
2021-06-02 01:12:54 +0000 <jg> im sorry :(, yea discord kills my laptop battery
2021-06-02 01:13:26 +0000 <jg> I wasted the better part of last night figuring out how to update my mirrors as I kept getting timeouts
2021-06-02 01:28:35 +0000 <liskin> oh well, I guess I'll just usbguard block-device the camera and call it a day
2021-06-02 01:29:20 +0000 <liskin> bonus is that I don't need to worry about covering the camera ever again
2021-06-02 01:37:38 +0000themainman(~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-06-02 01:38:08 +0000themainman(~themainma@user/themainman)
2021-06-02 01:41:03 +0000 <jg> was discord turning the camera/mic on without you asking?
2021-06-02 01:48:08 +0000wenzel(~wenzel@user/wenzel)
2021-06-02 01:57:32 +0000 <liskin> Not really, just preventing usb power management
2021-06-02 01:58:01 +0000 <liskin> But it probably could turn the camera on if it wanted to
2021-06-02 01:58:27 +0000 <liskin> And since it's closed source you never know what happens
2021-06-02 01:58:41 +0000 <liskin> Now nothing can use the camera
2021-06-02 01:59:16 +0000 <liskin> Anyway, I guess we should mention that X11 version thing somewhere
2021-06-02 01:59:31 +0000 <liskin> And fix a bunch of broken links on the website
2021-06-02 02:00:19 +0000 <liskin> Bloody hell it's a lot of work :-/
2021-06-02 02:01:03 +0000 <liskin> It's more than 5 years worth of technical debt
2021-06-02 02:01:27 +0000 <liskin> 3am here, night, bye
2021-06-02 02:31:30 +0000td_(~td@94.134.91.112) (Ping timeout: 264 seconds)
2021-06-02 02:33:10 +0000td_(~td@muedsl-82-207-238-043.citykom.de)
2021-06-02 02:44:14 +0000jg(~jrgiacone@47.149.222.98) (Remote host closed the connection)
2021-06-02 03:12:57 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)
2021-06-02 03:20:04 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Quit: leaving)
2021-06-02 03:31:17 +0000jg(~jrgiacone@47.149.222.98)
2021-06-02 04:23:07 +0000jg(~jrgiacone@47.149.222.98) (Quit: Lost terminal)
2021-06-02 06:01:35 +0000 <Solid> the best solution would be to not use discord :>
2021-06-02 06:19:28 +0000treetipglobe
2021-06-02 06:19:31 +0000globedeebo
2021-06-02 06:31:57 +0000wonko(~wjc@62.115.229.50)
2021-06-02 07:10:30 +0000bghimis(~bghimis@80.96.21.160) (Ping timeout: 264 seconds)
2021-06-02 07:10:35 +0000bghimis-(~bghimis@80.96.21.160)
2021-06-02 07:11:08 +0000cfricke(~cfricke@user/cfricke)
2021-06-02 07:12:08 +0000mc47(~yecinem@89.246.239.190)
2021-06-02 07:29:33 +0000 <mc47> liskin, is the stack.yaml in xmonad-contrib not supposed to work right now?
2021-06-02 07:31:42 +0000 <Solid> the x11 version is definitely just a mistake
2021-06-02 07:31:49 +0000 <Solid> but even then the xmonad version will cause problems
2021-06-02 07:33:59 +0000 <mc47> yeah I can't build it, I tried removing the x11 from extra-deps and it still can't build
2021-06-02 07:34:12 +0000 <mc47> which makes sense, since xmonad-0.17 doesn't exist
2021-06-02 07:34:26 +0000 <mc47> but how are we supposed to build till we make the release?
2021-06-02 07:35:00 +0000 <mc47> btw the activity these couple of days was quite refreshing \o/
2021-06-02 07:35:06 +0000 <Solid> indeed :)
2021-06-02 07:35:20 +0000 <Solid> what works for me is entering the correct x11 version (1.10) and pointing it to a local copy of xmonad $HEAD
2021-06-02 07:37:06 +0000 <mc47> I'm a stack newbie, you're doing the latter by specifying a path and a commit?
2021-06-02 07:37:14 +0000 <mc47> or do you just symlink xmonad in the root directory?
2021-06-02 07:38:08 +0000 <Solid> I just specify a path (and whatever commit that repo is on will be chosen) like `- /home/slot/repos/xmonad/xmonad-slotThe`
2021-06-02 07:39:17 +0000 <Solid> I guess this part sort of makes sense because at this point one can't build xmonad-contrib $HEAD and xmonad-0.15 together (due to the ExtensibleConfig changes)
2021-06-02 07:39:31 +0000 <Solid> so if you're building one git version you have to build the other one as well anyways
2021-06-02 07:44:36 +0000gruntsplatter(~jason@103.2.198.78)
2021-06-02 07:44:37 +0000 <mc47> that does make sense
2021-06-02 07:44:44 +0000 <mc47> thanks!
2021-06-02 07:46:18 +0000 <gruntsplatter> when I use xmonad and I move my mouse to where the gaps are my mouse jumps across the screen does anyone els have this issue with xmonad
2021-06-02 07:46:34 +0000 <gruntsplatter> is there a fix ?
2021-06-02 08:12:22 +0000themainman(~themainma@user/themainman) (Quit: WeeChat 3.1)
2021-06-02 08:14:01 +0000themainman(~themainma@user/themainman)
2021-06-02 08:16:41 +0000 <Solid> oh wow there are _a lot_ of matrix nicks here now
2021-06-02 08:16:47 +0000 <Solid> did some other channel get bridged?
2021-06-02 08:19:47 +0000 <mc47> yes, the one that wasn't bridged
2021-06-02 08:19:57 +0000 <mc47> the #xmonad channel
2021-06-02 08:20:12 +0000 <Solid> that's awesome
2021-06-02 08:20:25 +0000 <Solid> might want to add that one to the website as well then
2021-06-02 08:36:56 +0000gruntsplatter(~jason@103.2.198.78) (Quit: WeeChat 3.1)
2021-06-02 08:55:40 +0000 <liskin> Solid: maybe I should bridge the one Discord server I really want to be in to Matrix or something, yeah. :-/
2021-06-02 08:57:01 +0000 <Solid> liskin: yeah that's how I've done it with one server a few friends of mine insist on using (I'm bridging directly to IRC though)
2021-06-02 08:57:14 +0000 <Solid> the bridge itself is pretty bad, but improving it would involve me interacting with discord
2021-06-02 08:57:17 +0000 <Solid> and also writing js
2021-06-02 08:57:19 +0000 <Solid> so no :)
2021-06-02 10:11:47 +0000benin4(~benin@183.82.205.186)
2021-06-02 10:12:30 +0000benin(~benin@183.82.205.186) (Ping timeout: 272 seconds)
2021-06-02 10:12:30 +0000benin4benin
2021-06-02 10:42:38 +0000Guest7213(~Guest7213@78.32.70.245)
2021-06-02 10:45:07 +0000berberman(~berberman@user/berberman) (Ping timeout: 265 seconds)
2021-06-02 10:45:13 +0000berberman_(~berberman@user/berberman)
2021-06-02 11:43:21 +0000hpd[m](~hpdhpdeif@2001:470:69fc:105::230) ()
2021-06-02 11:57:48 +0000MrElendig(~Urist@user/mrelendig)
2021-06-02 12:16:41 +0000Guest73(~Guest73@124.40.244.150)
2021-06-02 12:18:06 +0000benin8(~benin@106.198.94.140)
2021-06-02 12:18:15 +0000 <Guest73> When using xmonad-git how can I look at documentation? Only in source or some place on hackage?
2021-06-02 12:19:55 +0000benin(~benin@183.82.205.186) (Ping timeout: 245 seconds)
2021-06-02 12:21:43 +0000benin(benin@gateway/vpn/protonvpn/benin)
2021-06-02 12:23:41 +0000benin8(~benin@106.198.94.140) (Ping timeout: 264 seconds)
2021-06-02 12:27:49 +0000 <Guest73> Any1
2021-06-02 12:28:48 +0000 <liskin> Guest73: you can build the html docs locally via cabal haddock or stack haddock, but it's not available anywhere on the web right now
2021-06-02 12:29:08 +0000 <liskin> it's somewhere in my todo list though
2021-06-02 12:30:30 +0000 <Guest73> Thanks. I will stick to code. No idea about cabal and stack. Not a Haskell programmer. Just a xmonad user.
2021-06-02 12:32:33 +0000 <liskin> Oh you're installing from distro? Might be a good idea to ask the maintainers to make a doc package as well.
2021-06-02 12:32:59 +0000 <liskin> In Debian, there is a docs package.
2021-06-02 12:33:06 +0000benin(benin@gateway/vpn/protonvpn/benin) (Ping timeout: 272 seconds)
2021-06-02 12:33:08 +0000 <liskin> (But there's no -git package :-/)
2021-06-02 12:33:36 +0000 <liskin> Possibly there already is a doc package for your distro?
2021-06-02 12:36:36 +0000Guest73(~Guest73@124.40.244.150) (Ping timeout: 250 seconds)
2021-06-02 12:47:04 +0000benin(~benin@183.82.205.186)
2021-06-02 12:55:06 +0000 <Solid> layouts are so weird
2021-06-02 12:56:37 +0000 <Solid> liskin: everything you said makes sense and yet the current solution for #281 still works, even with decorated layouts
2021-06-02 12:57:13 +0000 <Solid> I think if the check the description on both sides every time we can avoid not hiding the layouts though
2021-06-02 13:02:47 +0000 <liskin> that's really weird :-/
2021-06-02 13:05:51 +0000 <liskin> I think I might write a prop test or something
2021-06-02 13:06:45 +0000 <liskin> otherwise I'd have to rebase everything onto current masters and that might be more trouble, as I have some custom inspection instances for NewSelect and shit
2021-06-02 13:28:07 +0000 <liskin> but then I'd be tempted to clean up the tests and use hspec, so I'll just write a new xmonad config instead
2021-06-02 13:32:33 +0000 <Solid> hah
2021-06-02 13:33:25 +0000themainman(~themainma@user/themainman) (Read error: Connection reset by peer)
2021-06-02 13:34:00 +0000themainman(~themainma@user/themainman)
2021-06-02 13:42:46 +0000benin(~benin@183.82.205.186) (Ping timeout: 272 seconds)
2021-06-02 13:45:14 +0000 <liskin> okay I'm not crazy
2021-06-02 13:45:33 +0000 <liskin> I can reproduce dangling deco with main = xmonad bluetileConfig
2021-06-02 13:47:28 +0000 <liskin> open two terminals, mod-f to switch to fullscreen, mod-d to switch to tile2, now through the gap they can be seen and stay there after closing both terminals
2021-06-02 13:48:05 +0000 <liskin> that is, at 246600f70d6365c612ea9bfd31efd50c50a6c861, not at 0084a1af5c08fa3015af5aa2fd45d0c165d86a67
2021-06-02 14:07:36 +0000 <Solid> huh interesting
2021-06-02 14:07:41 +0000 <Solid> okay so that clears that up
2021-06-02 14:10:00 +0000benin(~benin@183.82.205.186)
2021-06-02 14:11:03 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-06-02 14:11:47 +0000 <liskin> Solid: I pushed a fixup
2021-06-02 14:11:47 +0000 <Solid> does 0084a1af5c08fa3015af5aa2fd45d0c165d86a67 fix this though? because it _should_ but I'm not sure of anything anymore right now :/
2021-06-02 14:12:01 +0000 <liskin> 0084a1af5c08fa3015af5aa2fd45d0c165d86a67 does fix it indeed
2021-06-02 14:12:34 +0000 <liskin> as I said, whenever you flip CL/CR outside of choose, some Hide messages might not get sent
2021-06-02 14:12:47 +0000 <liskin> or some extra Hides may get sent
2021-06-02 14:12:54 +0000 <liskin> which is what the fixup deals with
2021-06-02 14:13:17 +0000 <Solid> liskin: would that fixup not run into the same problems regarding having (CL, CL) and (CR, CR) as the first version?
2021-06-02 14:13:22 +0000 <liskin> I still don't understand what those flips were meant to do
2021-06-02 14:13:40 +0000 <liskin> it's not (CL, CL) et al that is the problem
2021-06-02 14:14:06 +0000 <liskin> the problem is when you switch to another layout without sending Hide to the old one
2021-06-02 14:14:34 +0000 <liskin> the fixup just stops a possible flicker when JumpToLayout is asked to switch to the current layout
2021-06-02 14:16:27 +0000 <Solid> ooooh okay
2021-06-02 14:17:17 +0000 <liskin> actually, I haven't tested the fixup
2021-06-02 14:17:32 +0000 <liskin> it's entirely possible it breaks it entirely
2021-06-02 14:18:28 +0000 <liskin> oh no it doesn't :-)
2021-06-02 14:18:46 +0000 <Solid> yeah can confirm it also works for me
2021-06-02 14:19:39 +0000 <liskin> anyway what I had in mind that the JumpToLayout handler can very likely be simplified further, if we're willing to risk calling handleMessage on both sides at all times
2021-06-02 14:27:29 +0000 <liskin> also, if the tree of layouts isn't exactly the right fold of a list, jumping to the layouts in the right subtree doesn't work :-/
2021-06-02 14:28:42 +0000 <liskin> with https://store.lisk.in/tmp/2021-06-02-152751_704x446_scrot.png I can't switch to Fullscreen
2021-06-02 14:33:28 +0000 <Solid> huh interesting
2021-06-02 14:33:33 +0000 <Solid> this this work originally?
2021-06-02 14:33:39 +0000 <Solid> s/this/did/
2021-06-02 14:34:36 +0000 <liskin> yeah I think before 246600f70d6365c612ea9bfd31efd50c50a6c861 handling of JumpToLayout would return Nothing when the layout wasn't there
2021-06-02 14:34:46 +0000 <liskin> and the logic relies on that
2021-06-02 14:35:46 +0000 <liskin> it's a bit weird though, hm, choose also returns Nothing sometimes
2021-06-02 14:36:48 +0000seschwar(~seschwar@user/seschwar)
2021-06-02 14:37:17 +0000 <liskin> but those nested cases might force a switch of CL to CR or the other way around even if the layout wasn't found, apparently
2021-06-02 14:41:50 +0000 <liskin> Solid: https://github.com/xmonad/xmonad/pull/281/files/0084a1af5c08fa3015af5aa2fd45d0c165d86a67..28ac3178…
2021-06-02 14:41:57 +0000 <liskin> oh not this one
2021-06-02 14:42:06 +0000 <liskin> this: https://github.com/xmonad/xmonad/pull/281/commits/3e05edfaf7dd5800ed0affcde2f7a400aa4e8abe
2021-06-02 14:42:42 +0000 <liskin> but we should probably really write the prop test after all, this is too brittle
2021-06-02 14:44:14 +0000 <Solid> liskin: oh that's really neat
2021-06-02 14:44:56 +0000 <Solid> is there infrastructure for message handling tests?
2021-06-02 14:45:28 +0000 <liskin> do you need more than just a call to handleMessage?
2021-06-02 14:46:12 +0000 <Solid> mh... probably not
2021-06-02 14:46:17 +0000 <liskin> the only possibly difficult bit is that type T uses Int as layout, but here you'll need something with both description and state to check that Hide was delivered
2021-06-02 14:46:31 +0000 <liskin> might just do a bit of bit arithmetic though
2021-06-02 14:56:07 +0000bghimis-(~bghimis@80.96.21.160) (WeeChat 3.1)
2021-06-02 14:57:48 +0000cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.1)
2021-06-02 15:32:19 +0000benin5(benin@gateway/vpn/protonvpn/benin)
2021-06-02 15:34:30 +0000benin(~benin@183.82.205.186) (Ping timeout: 264 seconds)
2021-06-02 15:34:31 +0000benin5benin
2021-06-02 15:45:15 +0000benin1(~benin@183.82.205.186)
2021-06-02 15:47:00 +0000benin(benin@gateway/vpn/protonvpn/benin) (Ping timeout: 245 seconds)
2021-06-02 15:47:01 +0000benin1benin
2021-06-02 18:26:44 +0000tremon(~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl)
2021-06-02 18:46:16 +0000wenzel(~wenzel@user/wenzel) (Read error: Connection reset by peer)
2021-06-02 18:46:36 +0000wenzel(~wenzel@user/wenzel)
2021-06-02 18:58:49 +0000wenzel(~wenzel@user/wenzel) (Quit: Leaving)
2021-06-02 19:39:31 +0000Guest73(~Guest73@124.40.244.150)
2021-06-02 19:41:29 +0000 <Guest73> Is there a way to add description to key bindings? I am thinking of generating help automatically.
2021-06-02 19:43:35 +0000 <liskin> Guest73: reminds me of https://old.reddit.com/r/xmonad/comments/nhu6uu/keybindings_generator/
2021-06-02 19:43:55 +0000 <liskin> also https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Util-NamedActions.html
2021-06-02 19:52:51 +0000 <Guest73> I liked this part: An additional step may be to have them displayed in a picture like those in the xmonad documentation
2021-06-02 19:56:22 +0000 <liskin> we have an open issue that mentions something similar: https://github.com/xmonad/xmonad/issues/287
2021-06-02 19:56:51 +0000 <liskin> (and I can almost guarantee I will not work on this myself)
2021-06-02 19:59:28 +0000Guest73(~Guest73@124.40.244.150) (Ping timeout: 250 seconds)
2021-06-02 20:00:19 +0000Guest73(~Guest73@124.40.244.150)
2021-06-02 20:03:20 +0000Guest73(~Guest73@124.40.244.150) (Client Quit)
2021-06-02 20:11:06 +0000benin0(benin@gateway/vpn/protonvpn/benin)
2021-06-02 20:13:30 +0000benin(~benin@183.82.205.186) (Ping timeout: 264 seconds)
2021-06-02 20:13:31 +0000benin0benin
2021-06-02 20:43:42 +0000lyiriyah[m](~lyiriyahm@2001:470:69fc:105::cc0)
2021-06-02 20:51:58 +0000 <lyiriyah[m]> Hi -- trying to figure out how to integrate IndependentScreens and PerWorkspace. IndependentScreens documentation doesn't really tell me anything. If anyone could should some insight that'd be great
2021-06-02 20:52:54 +0000lyiriyah52(~lyiriyah@host109-157-157-23.range109-157.btcentralplus.com)
2021-06-02 20:53:02 +0000lyiriyah52(~lyiriyah@host109-157-157-23.range109-157.btcentralplus.com) ()
2021-06-02 20:54:05 +0000benin(benin@gateway/vpn/protonvpn/benin) (Ping timeout: 245 seconds)
2021-06-02 21:01:58 +0000 <lyiriyah[m]> * Hi -- trying to figure out how to integrate IndependentScreens and PerWorkspace. IndependentScreens documentation doesn't really tell me anything. If anyone could share some insight that'd be great
2021-06-02 21:15:23 +0000mc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-06-02 21:19:59 +0000Guest7213(~Guest7213@78.32.70.245) (Quit: Client closed)
2021-06-02 21:26:50 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com) (Remote host closed the connection)
2021-06-02 21:27:00 +0000 <liskin> lyiriyah[m]: you can use https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Layout-IndependentScreens.html… to obtain a WorkspaceId to use in PerWorkspace
2021-06-02 21:28:24 +0000 <lyiriyah[m]> <liskin "lyiriyah: you can use https://ha"> Ok, but what is ScreenId?
2021-06-02 21:29:10 +0000geekosaur(~geekosaur@069-135-003-034.biz.spectrum.com)
2021-06-02 21:29:18 +0000 <liskin> lyiriyah[m]: you can just use a number, 0 being the primary screen, 1 being the next (in whatever order xinerama reports it to xmonad)
2021-06-02 21:29:27 +0000 <lyiriyah[m]> Oh I see
2021-06-02 21:29:30 +0000 <lyiriyah[m]> Thanks
2021-06-02 21:30:52 +0000 <lyiriyah[m]> How would I marshall more than one workspace?
2021-06-02 21:34:49 +0000 <liskin> *Main XMonad.Layout.IndependentScreens> map (marshall 1) ["one", "two"]
2021-06-02 21:34:51 +0000 <liskin> ["1_one","1_two"]
2021-06-02 21:35:17 +0000 <lyiriyah[m]> Ah, thanks so much. I'll give it a go
2021-06-02 21:41:17 +0000tremon(~tremon@217-63-61-89.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
2021-06-02 21:50:24 +0000habib(~habib@89.38.69.198)
2021-06-02 21:50:35 +0000habib(~habib@89.38.69.198) (Quit: habib)
2021-06-02 22:09:36 +0000seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-06-02 22:11:30 +0000 <liskin> geekosaur: what has to come from somewhere?
2021-06-02 22:12:07 +0000 <liskin> (we can continue the discussion there, just didn't want to add unnecessary noise by asking for this clarification)
2021-06-02 22:12:16 +0000 <geekosaur> GHC_ENVIRONMENT and friends
2021-06-02 22:12:34 +0000 <liskin> that would come from the build of xmonad library itself
2021-06-02 22:12:37 +0000 <geekosaur> you have to have somewhere to capture them from, so at least once have to build with cabal or stack
2021-06-02 22:13:08 +0000 <liskin> I kind of assumed cabal/stack set them when invoking ghc to build
2021-06-02 22:13:11 +0000 <geekosaur> oh. that's not certain to be the same as the one we need, though, especially if there are added deps
2021-06-02 22:13:26 +0000 <liskin> yes, that is a very legitimate concern
2021-06-02 22:14:37 +0000de-vri-es(~de-vri-es@voyager.de-vri.es) (Quit: Bathrobe!)
2021-06-02 22:15:05 +0000de-vri-es(~de-vri-es@voyager.de-vri.es)
2021-06-02 22:22:16 +0000 <geekosaur> come to think of it, when cabal or stack is building xmonad-contrib, it's doing so under /tmp
2021-06-02 22:22:35 +0000 <geekosaur> so the environment you capture potentially won't include it or xmonad
2021-06-02 22:23:30 +0000 <liskin> I thought it'd point somewhere in ~/.stack/snapshots or ./.stack-work/…
2021-06-02 22:23:53 +0000 <liskin> anyway, I'm leaning towards not even trying this
2021-06-02 22:24:22 +0000 <geekosaur> it may point under there but it's a PATH-like variable so it may point separately to a bunch of different package dirs
2021-06-02 22:24:23 +0000 <liskin> if cabal --package-env ~/.xmonad/ works, then cabal is a non-issue
2021-06-02 22:24:38 +0000 <geekosaur> only way to know is to try it and then hope they don''t change it
2021-06-02 22:24:50 +0000 <geekosaur> oh, I know that works, it was the first thing I tried
2021-06-02 22:25:05 +0000 <geekosaur> think I erased my setup afterward though
2021-06-02 22:25:26 +0000 <liskin> and for stack I think a more explicit approach like configuring the stack.yaml path or detecting stack.yaml at known locations seems like a better approach
2021-06-02 22:25:28 +0000 <geekosaur> yeh, it's gone now
2021-06-02 22:25:37 +0000 <liskin> I'm a bit confused about --package-env though
2021-06-02 22:25:45 +0000 <liskin> it sounds like such a perfect solutions
2021-06-02 22:25:51 +0000 <liskin> why isn't it recommended everywhere?
2021-06-02 22:26:30 +0000 <geekosaur> because most people work in terms of projects, not quasi-global installs
2021-06-02 22:26:58 +0000 <geekosaur> --package-env is what replaces global installs with cabal; for stack it's the global environment that replaces it
2021-06-02 22:27:22 +0000 <liskin> are you sure most people do that?
2021-06-02 22:27:40 +0000 <geekosaur> reasonably certain, yes
2021-06-02 22:27:43 +0000 <liskin> I thought most people just have a single xmonad.hs
2021-06-02 22:28:18 +0000 <geekosaur> oh, I was talkingg in general. I have no idea what most xmonad users do at this point
2021-06-02 22:28:21 +0000 <liskin> I mean, I consider myself an advanced xmonad "user" :-), and I had a single xmonad.hs until this year
2021-06-02 22:28:28 +0000 <geekosaur> exceot get confused at ancient instructions :)
2021-06-02 22:28:45 +0000 <liskin> oh
2021-06-02 22:29:00 +0000 <liskin> I meant why isn't it recommended for installing xmonad
2021-06-02 22:29:08 +0000 <geekosaur> actually I think most xmonad users install via system package manager and the really global env is still there
2021-06-02 22:29:44 +0000 <liskin> is it just that we haven't updated our instructions since cabal went v2 and 3rd party guides are a mess in general?
2021-06-02 22:30:26 +0000 <liskin> because if cabal install --package-env ~/.xmonad/ works just as well as the old v1 cabal install, then we should just recommend that
2021-06-02 22:30:38 +0000 <geekosaur> pretty much
2021-06-02 22:30:42 +0000 <liskin> oh, good point about package managers
2021-06-02 22:31:07 +0000 <liskin> arch people can probably even get the git version via their package manager
2021-06-02 22:31:26 +0000 <liskin> and as long as they manage to not run into dynamic linking breakage, they might live in blissful ignorance of cabal/stack
2021-06-02 22:32:06 +0000 <liskin> come to think of it, I should probably be qualified enough to provide builds of git xmonad for ubuntu and debian
2021-06-02 22:32:20 +0000 <liskin> brilliant, more things to put on my todo list :-D
2021-06-02 22:34:08 +0000 <geekosaur> evidently they patch xmonad to include -dynamic in its build command
2021-06-02 22:35:14 +0000wonko(~wjc@62.115.229.50) (Quit: See You Space Cowboy..)
2021-06-02 22:36:54 +0000 <liskin> understandably
2021-06-02 23:00:41 +0000benin0(~benin@183.82.205.186)
2021-06-02 23:00:54 +0000dmwit(~dmwit@pool-96-255-233-247.washdc.fios.verizon.net)