IRCBrowse

2023/03/22

2023-03-22 00:42:23 +0000doppo_(~doppo@2604:180::e0fc:a07f) (Ping timeout: 246 seconds)
2023-03-22 00:49:24 +0000doppo(~doppo@2604:180::e0fc:a07f)
2023-03-22 01:02:24 +0000vanvik(~vanvik@185.201.120.72) (Ping timeout: 248 seconds)
2023-03-22 02:22:03 +0000vanvik(~vanvik@185.201.120.72)
2023-03-22 03:04:24 +0000banc(~banc@154.47.24.195) (Ping timeout: 264 seconds)
2023-03-22 03:13:40 +0000td_(~td@i5387090D.versanet.de) (Ping timeout: 246 seconds)
2023-03-22 03:15:48 +0000td_(~td@i53870930.versanet.de)
2023-03-22 03:20:50 +0000banc(~banc@154.47.24.195)
2023-03-22 04:03:55 +0000doppo(~doppo@2604:180::e0fc:a07f) (Ping timeout: 248 seconds)
2023-03-22 04:04:55 +0000doppo(~doppo@2604:180::e0fc:a07f)
2023-03-22 04:13:46 +0000thunderrd(~thunderrd@183.182.111.130) (Ping timeout: 276 seconds)
2023-03-22 04:25:56 +0000thunderrd(~thunderrd@183.182.111.14)
2023-03-22 04:43:21 +0000sagax(~sagax_nb@user/sagax)
2023-03-22 05:59:53 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 256 seconds)
2023-03-22 06:01:54 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-03-22 06:15:53 +0000chomwitt(~chomwitt@2a02:587:7a19:3600:1ac0:4dff:fedb:a3f1)
2023-03-22 06:22:39 +0000Maeda(~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving)
2023-03-22 06:23:35 +0000Maeda(~Maeda@91-161-10-149.subs.proxad.net)
2023-03-22 06:39:17 +0000derfflinger(~derffling@user/derfflinger)
2023-03-22 06:55:20 +0000wusticality(~user@76.131.115.3) (Remote host closed the connection)
2023-03-22 07:34:26 +0000mncheckm(~mncheck@193.224.205.254)
2023-03-22 07:37:44 +0000thyriaen(~thyriaen@2a01:aea0:dd4:5328:6245:cbff:fe9f:48b1)
2023-03-22 07:39:15 +0000 <thyriaen> Howdy friends - I checked the docs and I was under the impression, that ~/.config/xmonad/xmonad.hs is supported in 0.17.1 -- but it doesn't load - Was I mistaken or is there some setting i am missing ?
2023-03-22 07:39:28 +0000 <thyriaen> ( I want to use it instead of ~/.xmonad/xmonad.hs
2023-03-22 07:41:48 +0000 <geekosaur> make sure ~/.xmonad doesn't exist
2023-03-22 07:42:10 +0000 <geekosaur> I've been using the XDG path for around a year without problems
2023-03-22 07:43:25 +0000 <Solid> We even check XDG dirs first in 0.17.0+, so it should definitely work
2023-03-22 07:45:04 +0000 <geekosaur> (it's around ~0345 here, why am I up?)
2023-03-22 07:45:07 +0000 <thyriaen> i deleted ~/.xmonad
2023-03-22 07:45:16 +0000 <thyriaen> and it doesn't load ~/.config/xmonad
2023-03-22 07:45:30 +0000 <thyriaen> and then creates ~/.xmonad new and uses the default config from within
2023-03-22 07:47:30 +0000 <Solid> can you post the output of `xmonad --version` and `xmonad --recompile` ?
2023-03-22 07:52:54 +0000 <thyriaen> Solid, sure
2023-03-22 07:53:41 +0000 <thyriaen> i have version 0.17.1
2023-03-22 07:55:22 +0000 <geekosaur> that's not quite enough. how is xmonad getting started and is it starting the correct xmonad? the path you have in a terminal may not be the one in effect when xmonad starts, so if yoy have two copies of xmonad the wrong one may be run
2023-03-22 07:55:42 +0000 <geekosaur> more specifically, do you have /usr/bin/xmonad and what version is it?
2023-03-22 07:58:01 +0000 <thyriaen> geekosaur, i only have one xmonad, from my package manager on a fresh install
2023-03-22 07:58:27 +0000 <thyriaen> running /usr/bin/xmonad --version gives 0.17.1
2023-03-22 07:58:40 +0000 <thyriaen> my output of recompile is:
2023-03-22 07:59:11 +0000 <thyriaen> "Xmonad will use ghc to recompile because neither /home/thyriaen/.xmonad/build nor /home/thyriaen/.xmonad/stack.yaml exsists
2023-03-22 07:59:15 +0000 <thyriaen> recompiling ( forced )
2023-03-22 07:59:21 +0000 <thyriaen> exited with success
2023-03-22 08:00:16 +0000 <thyriaen> "
2023-03-22 08:00:21 +0000geekosaurwonders if the xdg detection stuff needs debug output
2023-03-22 08:02:00 +0000derfflinger(~derffling@user/derfflinger) (Ping timeout: 255 seconds)
2023-03-22 08:02:04 +0000 <thyriaen> geekosaur, does the binary has to be present in the /.config/xmonad/ folder ?
2023-03-22 08:02:09 +0000 <thyriaen> because it isn't
2023-03-22 08:02:19 +0000 <thyriaen> it only is in the ~/.xmonad folder
2023-03-22 08:02:40 +0000 <Solid> no, when using XDG dirs the binary gets sent to $XDG_CACHE_HOME
2023-03-22 08:02:44 +0000 <geekosaur> that's because it's putting oit there, which means it picked the wrong folder
2023-03-22 08:03:49 +0000 <thyriaen> geekosaur, could it be that when starting up and xmonad get's loaded at that time my xdg stuff isn't set yet so it can't find the .config folder ?
2023-03-22 08:04:16 +0000 <Solid> Oh, nvmd, we do not prefer XDG dirs
2023-03-22 08:04:32 +0000 <Solid> only the XMonad env vars
2023-03-22 08:05:03 +0000 <Solid> thyriaen: it's first looking for either `xmonad.hs`, or `build` inside of ~/.xmonad
2023-03-22 08:05:06 +0000 <geekosaur> we don't require the xdg envars although we use them if present, if I recall the code correctly
2023-03-22 08:05:21 +0000 <Solid> yeah all those env vars have a fallback
2023-03-22 08:05:28 +0000 <Solid> like ~/.config etc.
2023-03-22 08:05:32 +0000 <thyriaen> ic
2023-03-22 08:05:38 +0000 <thyriaen> but
2023-03-22 08:05:42 +0000 <thyriaen> when i delete ~/.xmonad
2023-03-22 08:05:44 +0000 <thyriaen> and reboot
2023-03-22 08:05:47 +0000 <thyriaen> it get's recreated
2023-03-22 08:05:54 +0000 <thyriaen> even thought i have an ~/.config/xmonad/xmonad.hs
2023-03-22 08:06:48 +0000 <geekosaur> that's wrong. I could have sworn we look specifically for where xmonad.hs is, and check the xdg dir first (well, we check the xmonad envar first, then the xdg dir, then fallback to ~/.xmonad)
2023-03-22 08:07:15 +0000 <Solid> I was thinking that as well, but we explicitly check `xmEnvDirs <|> xmDirs <|> xdgDirs`
2023-03-22 08:07:23 +0000 <Solid> And the docs agree and weren't changed for a while
2023-03-22 08:07:59 +0000 <Solid> but we *do* check for xmonad.hs or build explicitly
2023-03-22 08:08:06 +0000 <Solid> not just for the presence of the directory
2023-03-22 08:08:38 +0000 <geekosaur> right, that was the fix for random unfixed contribs creating data files explicitly in ~/.xmonad (hello prompt)
2023-03-22 08:09:00 +0000 <Solid> thyriaen: only thing I can think of is that there is some old version of xmonad somewhere that gets used for the first recompilation step
2023-03-22 08:09:55 +0000 <thyriaen> Solid, as I said, it is a fresh install with only one xmonad version
2023-03-22 08:11:29 +0000 <geekosaur> just for grins and giggles: you don't happen to have $XMONAD_CONFIG_DIR set do you?
2023-03-22 08:11:38 +0000 <thyriaen> let me check
2023-03-22 08:12:07 +0000 <thyriaen> echo $XMONAD_CONFIG_DIR returns a empty line
2023-03-22 08:15:54 +0000 <geekosaur> odd. I know this works because I've been using it
2023-03-22 08:16:50 +0000 <thyriaen> geekosaur, any ideas what else i can check ?
2023-03-22 08:17:15 +0000 <geekosaur> no, I'm pretty lost at this point
2023-03-22 08:17:17 +0000 <deebo> check yourself, before you wreck yourself
2023-03-22 08:17:18 +0000 <geekosaur> 😞
2023-03-22 08:17:41 +0000 <thyriaen> maybe the launch script of my display manager
2023-03-22 08:17:44 +0000 <thyriaen> is wrong
2023-03-22 08:17:47 +0000 <thyriaen> where can i find that ?
2023-03-22 08:18:09 +0000 <geekosaur> depends on the display manager but often /usr/share/xsessions
2023-03-22 08:18:42 +0000 <thyriaen> geekosaur, it just execs xmonad-start
2023-03-22 08:19:25 +0000 <geekosaur> so now you need to find that, which I presume is a script
2023-03-22 08:20:14 +0000 <thyriaen> geekosaur, yes it is
2023-03-22 08:20:20 +0000 <thyriaen> it is in /usr/bin/
2023-03-22 08:20:40 +0000 <thyriaen> it does a lot of directory stuff
2023-03-22 08:20:43 +0000 <thyriaen> let me show you
2023-03-22 08:22:16 +0000 <geekosaur> (btw you don't have to keep pinging me)
2023-03-22 08:23:14 +0000 <thyriaen> i think it is a habbit
2023-03-22 08:25:51 +0000 <thyriaen> paste.tomsmeding.com/fFNtjbVb
2023-03-22 08:27:00 +0000 <geekosaur> yeh, that's creating ~/.xmonad and copying their idea of a default config into it
2023-03-22 08:29:34 +0000 <thyriaen> geekosaur, and xmonad-start is provided by my distribution ?
2023-03-22 08:29:44 +0000 <geekosaur> if you change the xsession desktop file to run xmonad directly instead, things should work as they're supposed to
2023-03-22 08:29:53 +0000 <geekosaur> yes, this came from your distro
2023-03-22 08:30:04 +0000 <thyriaen> geekosaur, so just instead of xmonad-start i just exec xmonad ?
2023-03-22 08:31:54 +0000 <geekosaur[m]> Yes
2023-03-22 08:33:22 +0000 <thyriaen> thanks a lot geekosaur, it works now :p
2023-03-22 08:42:31 +0000 <geekosaur> you should probably file a bug against your distro that they should check ~/.config/xmonad before forcing ~/.xmonad
2023-03-22 08:43:48 +0000 <geekosaur> and possibly should default to XDG for new installs
2023-03-22 08:57:57 +0000 <thyriaen> geekosaur, i will try to do that
2023-03-22 08:58:04 +0000derfflinger(~derffling@user/derfflinger)
2023-03-22 09:50:50 +0000banc(~banc@154.47.24.195) (Quit: Bye, bye)
2023-03-22 09:57:51 +0000ft(~ft@p3e9bc443.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2023-03-22 11:14:31 +0000derfflinger(~derffling@user/derfflinger) (Ping timeout: 240 seconds)
2023-03-22 11:29:44 +0000thyriaen(~thyriaen@2a01:aea0:dd4:5328:6245:cbff:fe9f:48b1) (Remote host closed the connection)
2023-03-22 12:21:27 +0000derfflinger(~derffling@user/derfflinger)
2023-03-22 13:40:33 +0000thunderrd(~thunderrd@183.182.111.14) (Ping timeout: 268 seconds)
2023-03-22 13:53:06 +0000thunderrd(~thunderrd@183.182.111.220)
2023-03-22 14:18:55 +0000sagax(~sagax_nb@user/sagax) (Ping timeout: 276 seconds)
2023-03-22 14:48:48 +0000alethkit(23bd17ddc6@sourcehut/user/alethkit) (Remote host closed the connection)
2023-03-22 14:48:48 +0000zoglesby(f0f8ca1525@user/zoglesby) (Remote host closed the connection)
2023-03-22 14:48:48 +0000samhh(7569f027cf@2604:bf00:561:2000::e4) (Remote host closed the connection)
2023-03-22 14:50:08 +0000zoglesby(f0f8ca1525@2604:bf00:561:2000::64)
2023-03-22 14:50:08 +0000zoglesby(f0f8ca1525@2604:bf00:561:2000::64) (Changing host)
2023-03-22 14:50:08 +0000zoglesby(f0f8ca1525@user/zoglesby)
2023-03-22 14:50:35 +0000samhh(7569f027cf@2604:bf00:561:2000::e4)
2023-03-22 14:51:44 +0000alethkit(23bd17ddc6@sourcehut/user/alethkit)
2023-03-22 15:50:33 +0000zoglesby(f0f8ca1525@user/zoglesby) (Remote host closed the connection)
2023-03-22 15:50:33 +0000alethkit(23bd17ddc6@sourcehut/user/alethkit) (Write error: Broken pipe)
2023-03-22 15:50:34 +0000samhh(7569f027cf@2604:bf00:561:2000::e4) (Remote host closed the connection)
2023-03-22 15:50:57 +0000derfflinger(~derffling@user/derfflinger) (Quit: Leaving)
2023-03-22 15:55:08 +0000zoglesby(f0f8ca1525@user/zoglesby)
2023-03-22 15:56:12 +0000alethkit(23bd17ddc6@sourcehut/user/alethkit)
2023-03-22 15:56:52 +0000samhh(7569f027cf@2604:bf00:561:2000::e4)
2023-03-22 16:00:11 +0000lilua[m](~liluamatr@2001:470:69fc:105::3:1c9e) (Quit: You have been kicked for being idle)
2023-03-22 16:23:20 +0000rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca)
2023-03-22 16:36:33 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 246 seconds)
2023-03-22 16:38:32 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-03-22 17:54:48 +0000malook(~Thunderbi@46.52.72.170)
2023-03-22 17:57:17 +0000matijja(~matijja@193.77.181.201) (Quit: ZNC 1.8.2 - https://znc.in)
2023-03-22 17:59:10 +0000matijja(~matijja@193.77.181.201)
2023-03-22 18:00:59 +0000matijja(~matijja@193.77.181.201) (Client Quit)
2023-03-22 18:01:34 +0000matijja(~matijja@193.77.181.201)
2023-03-22 18:30:55 +0000malook(~Thunderbi@46.52.72.170) (Quit: malook)
2023-03-22 19:53:02 +0000ft(~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-03-22 20:10:30 +0000ft(~ft@p3e9bc443.dip0.t-ipconnect.de) (Remote host closed the connection)
2023-03-22 20:19:34 +0000ft(~ft@p3e9bc443.dip0.t-ipconnect.de)
2023-03-22 20:37:40 +0000srz(~srz@181.228.49.93)
2023-03-22 21:14:58 +0000yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de) (Quit: Leaving)
2023-03-22 21:27:59 +0000srz(~srz@181.228.49.93) (Ping timeout: 268 seconds)
2023-03-22 21:34:17 +0000yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de)
2023-03-22 21:57:29 +0000rekahsoft(~rekahsoft@bras-base-orllon1122w-grc-07-174-95-68-142.dsl.bell.ca) (Ping timeout: 246 seconds)
2023-03-22 22:38:37 +0000chomwitt(~chomwitt@2a02:587:7a19:3600:1ac0:4dff:fedb:a3f1) (Ping timeout: 265 seconds)
2023-03-22 23:07:12 +0000srz(~srz@181.228.49.93)
2023-03-22 23:43:40 +0000vifon(~vifon@user/vifon) (Ping timeout: 252 seconds)
2023-03-22 23:44:03 +0000vifon(~vifon@nixon.einval.eu)
2023-03-22 23:45:37 +0000vifon(~vifon@nixon.einval.eu) (Client Quit)
2023-03-22 23:45:50 +0000vifon(~vifon@nixon.einval.eu)
2023-03-22 23:51:31 +0000haskl[error](~haskl@user/haskl)
2023-03-22 23:51:33 +0000haskl(~haskl@user/haskl) (Read error: Connection reset by peer)
2023-03-22 23:54:01 +0000srz(~srz@181.228.49.93) (Ping timeout: 240 seconds)
2023-03-22 23:55:20 +0000vifon(~vifon@nixon.einval.eu) (Changing host)
2023-03-22 23:55:20 +0000vifon(~vifon@user/vifon)