2024/07/02

Newest at the top

2024-07-02 18:03:23 +0200lambdabot(~lambdabot@haskell/bot/lambdabot)
2024-07-02 18:02:03 +0200lambdabot(~lambdabot@haskell/bot/lambdabot) (Remote host closed the connection)
2024-07-02 17:19:55 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 246 seconds)
2024-07-02 16:48:00 +0200catman(~catman@user/catman)
2024-07-02 14:14:01 +0200eColi888(~eColi888@user/eColi888) (Quit: leaving)
2024-07-02 14:10:01 +0200eColi888(~eColi888@user/eColi888)
2024-07-02 13:36:54 +0200cfricke(~cfricke@user/cfricke)
2024-07-02 11:50:15 +0200ChubaDuba(~ChubaDuba@46.147.208.129) (Quit: Leaving)
2024-07-02 11:43:36 +0200ChubaDuba(~ChubaDuba@46.147.208.129)
2024-07-02 11:20:49 +0200cfricke(~cfricke@user/cfricke) (Ping timeout: 256 seconds)
2024-07-02 10:54:58 +0200ft(~ft@p4fc2ab80.dip0.t-ipconnect.de) (Quit: leaving)
2024-07-02 10:30:49 +0200L29Ah(~L29Ah@wikipedia/L29Ah)
2024-07-02 09:13:35 +0200cfricke(~cfricke@user/cfricke)
2024-07-02 08:36:57 +0200catman(~catman@user/catman) (Read error: Connection reset by peer)
2024-07-02 08:07:11 +0200Nixkernal(~Nixkernal@240.17.194.178.dynamic.cust.swisscom.net) (Ping timeout: 264 seconds)
2024-07-02 07:27:44 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Read error: Connection timed out)
2024-07-02 05:50:06 +0200 <haskellbridge> <iqubic (she/her)> Good to know.
2024-07-02 05:49:10 +0200 <geekosaur> along with your compiled config, xmonad.errors (output from compiling your config), and things like XMonad.Prompt saved history
2024-07-02 05:48:34 +0200 <geekosaur> if you set all of `XMONAD_DATA_DIR`, `XMONAD_CONFIG_DIR`, and `XMONAD_CACHE_DIR` are set in the environment then it'll be in `XMONAD_CACHE_DIR`
2024-07-02 05:47:14 +0200 <haskellbridge> <iqubic (she/her)> Thanks. I've just told nix to stop explicitly managing xmonad for me, and now things seems to be working a lot better.
2024-07-02 05:45:51 +0200 <geekosaur> everything including state is in ~/.xmonad if your xmonad.hs is there, otherwise it's ~/.cache/xmonad
2024-07-02 05:45:03 +0200 <haskellbridge> <iqubic (she/her)> What's the state dir for xmoand?
2024-07-02 05:44:47 +0200 <haskellbridge> <iqubic (she/her)> I didn't actually know that.
2024-07-02 05:44:04 +0200 <geekosaur> as usual for Haskell, it's implicitly `module Main where` because it doesn't have a module declaration
2024-07-02 05:42:48 +0200 <haskellbridge> <iqubic (she/her)> Do you need your xmonad.hs to declare itself a module? You aren't doing that...
2024-07-02 05:37:23 +0200 <geekosaur> I'm not sure it's even necessary any more, that code's fairly solid at this point
2024-07-02 05:35:59 +0200 <geekosaur> no, it's basically an informational diagnostic to help you verify that it's doing the right thing
2024-07-02 05:34:27 +0200 <haskellbridge> <iqubic (she/her)> That's what I'm getting from running "xmonad --recompile" right now.
2024-07-02 05:34:08 +0200 <haskellbridge> <iqubic (she/her)> XMonad will use ghc to recompile, because none of "/home/sophia/.xmonad/build", "/home/sophia/.xmonad/stack.yaml", "/home/sophia/.xmonad/flake.nix", "/home/sophia/.xmonad/default.nix" exist.
2024-07-02 05:34:07 +0200 <haskellbridge> <iqubic (she/her)> Should I be worried about this warning?
2024-07-02 05:32:42 +0200 <haskellbridge> <iqubic (she/her)> Nix did mess with that a bit, but I just told nix to stop messing with it so I could do this on my own.
2024-07-02 05:32:18 +0200 <haskellbridge> <iqubic (she/her)> I do now have ~/.xmonad/xmonad.hs and things are using that.
2024-07-02 05:32:12 +0200 <geekosaur> I don't know if nix messes with this, which is possible with environment variables
2024-07-02 05:31:45 +0200 <geekosaur> you shouldn't have both, but supposedly if you have ~/.xmonad/xmonad.hs then everything should use ~/.xmonad
2024-07-02 05:30:51 +0200 <haskellbridge> <iqubic (she/her)> I didn't, but now I do.
2024-07-02 05:30:11 +0200 <geekosaur> hm. do you happen to have both ~/.xmonad and ~/.config/xmonad (or at least ~/.cache/xmonad) for some reason?
2024-07-02 05:27:47 +0200 <haskellbridge> <iqubic (she/her)> Yeah... It was compiling my config properly, but then proceeding to continue to use an older version of my config.
2024-07-02 05:27:14 +0200 <geekosaur> which is actually what I was checking for with that suggestion
2024-07-02 05:26:34 +0200 <geekosaur> s/element/field
2024-07-02 05:26:27 +0200 <geekosaur> that would be weird because the code I gave you would have thrown an error long the lines of "XPConfig has no element prevCompletionKey"
2024-07-02 05:25:49 +0200 <haskellbridge> <iqubic (she/her)> Also, xmonad not restarting properly has been fixed too.
2024-07-02 05:25:20 +0200 <haskellbridge> <iqubic (she/her)> I have a much better way of configuring xmonad now that actually works well, and lets me specify whichever version of xmonad I need..
2024-07-02 05:24:42 +0200 <haskellbridge> <iqubic (she/her)> geekosaur: Turns out all the issues I was having with shift-tab doing weird things was due to somehow using an older version of xmonad-contrib despite using xmonad 0.18. I'm not sure how this version mismatch happened, but I blame nix.
2024-07-02 04:46:36 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::)
2024-07-02 04:43:35 +0200terrorjack(~terrorjac@2a01:4f8:c17:87f8::) (Quit: The Lounge - https://thelounge.chat)
2024-07-02 04:43:20 +0200td_(~td@i53870908.versanet.de)
2024-07-02 04:41:39 +0200td_(~td@i53870923.versanet.de) (Ping timeout: 264 seconds)
2024-07-02 04:41:20 +0200 <haskellbridge> <iqubic (she/her)> Yep. I see.
2024-07-02 04:41:07 +0200 <geekosaur> the XMONAD_RESTART message handler does `restart "xmonad" True`, `"xmonad"` is passed to `executeFile`, which searches `$PATH`
2024-07-02 04:41:01 +0200 <haskellbridge> <iqubic (she/her)> I see. That makes sesne.