2024/02/22

2024-02-22 00:04:22 +0100todi(~todi@p4fd1a2f5.dip0.t-ipconnect.de)
2024-02-22 04:20:59 +0100td_(~td@i53870902.versanet.de) (Ping timeout: 264 seconds)
2024-02-22 04:22:23 +0100td_(~td@i53870910.versanet.de)
2024-02-22 06:54:13 +0100down200(~down200@shell.lug.mtu.edu)
2024-02-22 08:45:11 +0100hightower3(~hightower@dh207-114-78.xnet.hr)
2024-02-22 08:48:29 +0100hightower2(~hightower@dh207-80-183.xnet.hr) (Ping timeout: 272 seconds)
2024-02-22 09:36:49 +0100Miroboru(~myrvoll@178-164-114.82.3p.ntebredband.no) (Remote host closed the connection)
2024-02-22 10:08:17 +0100julie_pilgrim(~julie_pil@user/julie-pilgrim/x-1240752)
2024-02-22 10:22:08 +0100Miroboru(~myrvoll@178-164-114.82.3p.ntebredband.no)
2024-02-22 10:23:42 +0100ft(~ft@p508db2e6.dip0.t-ipconnect.de) (Quit: leaving)
2024-02-22 10:25:16 +0100cfricke(~cfricke@user/cfricke)
2024-02-22 10:39:10 +0100julie_pilgrim(~julie_pil@user/julie-pilgrim/x-1240752) (Remote host closed the connection)
2024-02-22 10:49:26 +0100julie_pilgrim(~julie_pil@user/julie-pilgrim/x-1240752)
2024-02-22 10:53:48 +0100julie_pilgrim(~julie_pil@user/julie-pilgrim/x-1240752) (Ping timeout: 250 seconds)
2024-02-22 11:55:11 +0100Miroboru(~myrvoll@178-164-114.82.3p.ntebredband.no) (Ping timeout: 264 seconds)
2024-02-22 12:50:58 +0100Miroboru(~myrvoll@178-164-114.82.3p.ntebredband.no)
2024-02-22 14:10:41 +0100lampilelo(~user@178.216.137.1)
2024-02-22 16:32:14 +0100vanvik(~vanvik@78.156.10.140) (Quit: Ping timeout (120 seconds))
2024-02-22 16:32:35 +0100vanvik(~vanvik@78.156.10.140)
2024-02-22 16:43:47 +0100beastwick(~brian@user/beastwick)
2024-02-22 17:03:52 +0100 <beastwick> So, I am really into xmonad now, are there future plans for a wayland port or rewrite?
2024-02-22 17:04:09 +0100 <L29Ah> no
2024-02-22 17:04:23 +0100 <L29Ah> but you can join waymonad if you feel like it's the way to go
2024-02-22 17:05:09 +0100 <beastwick> I am fine with X for the foreseeable future, but I feel like wayland is eventually going to be the target platform in a few years
2024-02-22 17:05:50 +0100 <vrs> it's a bit like fusion except it's five years instead of 20
2024-02-22 17:06:04 +0100 <beastwick> fusion?
2024-02-22 17:06:31 +0100 <vrs> the joke goes that fusion power is the energy of the future, it was 20 years away in 1970 and it is 20 years away in 2020
2024-02-22 17:06:45 +0100 <beastwick> that's an apt joke
2024-02-22 17:07:21 +0100 <beastwick> I tried using wayland a couple of days ago, but it seems like there are some extra things I have to do with a current nvidia gpu, it wasn't as easy as a startx.
2024-02-22 17:07:44 +0100 <beastwick> and some of the out of box de's like kde/gnome just fail for me on something like debian
2024-02-22 17:07:56 +0100 <beastwick> with wayland, which I thought was really surprising
2024-02-22 17:08:35 +0100 <liskin> vrs: lol indeed :-)
2024-02-22 17:08:43 +0100 <geekosaur> there aren't concrete plans, but see https://discourse.haskell.org/t/haskell-wlroots-bindings/8426/47 where the community has been updating wlroots as a first step toward a wayland rewrite
2024-02-22 17:09:31 +0100 <geekosaur> although I haven't seen any updates in a while
2024-02-22 17:54:08 +0100L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 256 seconds)
2024-02-22 18:01:42 +0100cfricke(~cfricke@user/cfricke) (Quit: WeeChat 4.1.2)
2024-02-22 20:34:42 +0100L29Ah(~L29Ah@wikipedia/L29Ah)
2024-02-22 21:17:30 +0100Guest47(~Guest47@231.11.11.93.rev.sfr.net)
2024-02-22 21:24:53 +0100 <Guest47> Hi, I feel a bit stupid… I thought I knew haskell, but I am now completely at lost trying to install/recompile xmonad on ubuntu 22.04. I tried using the apt packages, I tried to compile xmonad from source : it seems to work (I have an xmonad executable) but the "xmonad --recompile" invariably fails with the following message
2024-02-22 21:24:53 +0100 <Guest47> Monad will use ghc to recompile, because none of "/home/sla/.xmonad/build", "/home/sla/.xmonad/stack.yaml", "/home/sla/.xmonad/flake.nix", "/home/sla/.xmonad/default.nix" exist.
2024-02-22 21:24:54 +0100 <Guest47> XMonad recompiling (forced).
2024-02-22 21:24:54 +0100 <Guest47> Errors detected while compiling xmonad config: /home/sla/.xmonad/xmonad.hs
2024-02-22 21:24:55 +0100 <Guest47> $ ghc --make xmonad.hs -i -ilib -fforce-recomp -main-is main -v0 -outputdir /home/sla/.xmonad/build-x86_64-linux -o /home/sla/.xmonad/xmonad-x86_64-linux
2024-02-22 21:24:55 +0100 <Guest47> xmonad.hs:3:1: error:
2024-02-22 21:24:56 +0100 <Guest47>     Could not find module ‘XMonad’
2024-02-22 21:24:56 +0100 <Guest47>     Use -v (or `:set -v` in ghci) to see a list of the files searched for.
2024-02-22 21:24:57 +0100 <Guest47>   |
2024-02-22 21:24:57 +0100 <Guest47> 3 | import XMonad
2024-02-22 21:24:58 +0100 <Guest47>   | ^^^^^^^^^^^^^
2024-02-22 21:24:58 +0100 <Guest47> xmonad.hs:4:1: error:
2024-02-22 21:24:59 +0100 <Guest47>     Could not find module ‘XMonad.Util.EZConfig’
2024-02-22 21:24:59 +0100 <Guest47>     Use -v (or `:set -v` in ghci) to see a list of the files searched for.
2024-02-22 21:25:00 +0100 <Guest47>   |
2024-02-22 21:25:00 +0100 <Guest47> 4 | import XMonad.Util.EZConfig (additionalKeysP)
2024-02-22 21:25:01 +0100 <Guest47>   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2024-02-22 21:25:01 +0100 <Guest47> xmonad.hs:5:1: error:
2024-02-22 21:25:14 +0100 <Guest47> These file exist though
2024-02-22 21:26:27 +0100 <geekosaur> if using apt, it is not enough to install the xmonad package; you also need libghc-xmonad-dev and libghc-xmonad-contrib-dev
2024-02-22 21:26:35 +0100 <Guest47> I mean the file "/home/sla/.xmonad/stack.yaml" exists
2024-02-22 21:27:44 +0100 <Guest47> building from source is not sufficient ?
2024-02-22 21:27:58 +0100ft(~ft@p508db2e6.dip0.t-ipconnect.de)
2024-02-22 21:27:59 +0100 <geekosaur> building from source will depend on how you do it
2024-02-22 21:28:31 +0100 <Guest47> I followed the instructions on the website's pages…
2024-02-22 21:29:08 +0100 <geekosaur> I meant cabal vs. stack vs. nix
2024-02-22 21:29:19 +0100 <Guest47> I used stack
2024-02-22 21:29:39 +0100 <geekosaur> if you used stack then you need to make sure the stack.yaml is found so --recompile will use stack's build
2024-02-22 21:29:47 +0100hightower4(~hightower@dh207-80-70.xnet.hr)
2024-02-22 21:30:21 +0100 <geekosaur> that said this sounds, hm. lemme check
2024-02-22 21:31:43 +0100 <geekosaur> okahy, yes, looks like you have 0.18.0
2024-02-22 21:32:02 +0100 <Guest47> OK… I get the message telling me that the "/home/sla/.xmonad/stack.yaml" does not exists while, to me, it is the one that I used when compiling
2024-02-22 21:32:15 +0100hightower3(~hightower@dh207-114-78.xnet.hr) (Ping timeout: 256 seconds)
2024-02-22 21:32:23 +0100 <Guest47> Yes, 0.18
2024-02-22 21:32:51 +0100 <Guest47>  xmonad --version
2024-02-22 21:32:51 +0100 <Guest47> xmonad 0.18.0.9
2024-02-22 21:33:33 +0100 <geekosaur> huh, build from git? that wouldn't use stack unless you've done some custom setup; stack would use the xmonad version from the resolver you specified
2024-02-22 21:35:23 +0100 <Guest47> I merely followed the instructions there : https://xmonad.org/INSTALL.html#build-using-stack
2024-02-22 21:36:47 +0100 <geekosaur> right, I just went through that and it would use a version from a resolver, which would not have a .9 suffix
2024-02-22 21:36:48 +0100 <Guest47> Just before that part, they tell you to git clone the xmonad and xmonad-contrib
2024-02-22 21:37:24 +0100 <geekosaur> oh, I see, `stack init` sees the checkouts and does the extra setup, sorry
2024-02-22 21:37:28 +0100 <geekosaur> I'm not a stack user
2024-02-22 21:37:50 +0100 <Guest47> Nor am I, it seems ;)
2024-02-22 21:38:45 +0100 <geekosaur> still, the message says it isn't seeing the stack.yaml. the code to check for it looked correct to me though
2024-02-22 21:40:20 +0100 <Guest47> I indeed feel it’s an issue between stack and the ghc version installed on my system ? it is where my understanding of the stack/ghc system fails…
2024-02-22 21:40:47 +0100 <geekosaur> stack isn't even becoming involved, since xmonad isn't seeing your stack.yaml
2024-02-22 21:41:17 +0100 <geekosaur> so it's probably running the ghc installed via apt, which won't be able to see anything installed via stack (this is deliberate)
2024-02-22 21:42:00 +0100 <Guest47>  I used ghcup to install ghc
2024-02-22 21:42:56 +0100 <Guest47> I tried to start from a blank state, removing first all the apt stuff
2024-02-22 21:43:24 +0100 <geekosaur> stack won't use that one either unless you installed the stack hook, and it won't see anything installed via stack
2024-02-22 21:46:49 +0100 <Guest47> OK, I think I understand what you’re saying. Building from source using stack uses a separate installation of the ghc toolchain (that’s the point of stack, to allow repeatable builds), but xmonad --recompile uses another
2024-02-22 21:48:26 +0100 <geekosaur> if xmonad sees stack.yaml then it should use stack to do the rebuild, which will use the correct stack toolchain
2024-02-22 21:48:49 +0100 <geekosaur> so the root problem is it's not seeing your stack.yaml for some reason and then using the wrong ghc as a result
2024-02-22 21:49:50 +0100 <geekosaur> did you symlink your stack.yaml into your xmonad directory by any chance? you might make sure the symlink is correct in that case
2024-02-22 21:51:53 +0100 <Guest47> I found the issue : that is a very stupid one indeed. The https://xmonad.org/INSTALL.html#build-using-stack instructions tell you to git clone and build in .config/xmonad, not .xmonad !
2024-02-22 21:52:24 +0100 <Guest47> so the path is indeed wrong
2024-02-22 21:52:55 +0100 <geekosaur> ok, only partially converted to XDG
2024-02-22 21:53:05 +0100 <geekosaur> Solid ^^
2024-02-22 21:53:43 +0100 <geekosaur> (if you put your config in ~/.config/xmonad instead of ~/.xmonad then xmonad uses XDG paths)
2024-02-22 21:59:23 +0100 <Guest47> Yes!!! I had a conflicting version under ~/.xmonad ! Thank you VERY VERY much !!!
2024-02-22 22:21:04 +0100Guest47(~Guest47@231.11.11.93.rev.sfr.net) (Ping timeout: 250 seconds)
2024-02-22 23:09:05 +0100bwolf(c3bc363dd1@2a03:6000:1812:100::180)
2024-02-22 23:37:56 +0100down200(~down200@shell.lug.mtu.edu) (Quit: ZNC - https://znc.in)
2024-02-22 23:39:56 +0100down200(~down200@shell.lug.mtu.edu)