2023/04/11

2023-04-11 00:11:36 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: Lost terminal)
2023-04-11 00:20:07 +0000catman(~catman@user/catman)
2023-04-11 00:50:45 +0000hightower2(~hightower@213.149.51.70)
2023-04-11 01:13:52 +0000Guest191(~Guest19@2404:130:0:1000:5484:a8db:f032:5999)
2023-04-11 01:20:23 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-11 01:25:40 +0000blaa(~bla@83.24.86.118.ipv4.supernova.orange.pl) (Ping timeout: 252 seconds)
2023-04-11 01:27:12 +0000bla(~bla@79.191.151.29.ipv4.supernova.orange.pl)
2023-04-11 01:28:52 +0000 <Guest191> For people using XMonad and Gnome together... https://xmonad.org/gnome.html says "A Gnome session for xmonad is part of the distribution package, however it is out of date.  You can use the gnome-session-xmonad PPA to get an updated version." and links to https://launchpad.net/~gekkio/+archive/ubuntu/xmonad for that PPA, which in turn documents
2023-04-11 01:28:53 +0000 <Guest191> "Gnome+XMonad session package
2023-04-11 01:28:53 +0000 <Guest191> The xmonad package no longer contains Gnome session files, so I'm maintaining them here:" linking to https://github.com/Gekkio/gnome-session-xmonad -- which has been archived with the notice "Update 12/2022: I've switched to Pop!_OS and its tiling window manager, and have no plans to update this repository/package anymore!".  So I'm wondering
2023-04-11 01:28:54 +0000 <Guest191> whether anyone knows of any plans for maintaining this moving forwards?
2023-04-11 02:10:02 +0000lordhorzion(~horzion@ProtonDB/horzion) (Remote host closed the connection)
2023-04-11 02:10:19 +0000lordhorzion(~horzion@ProtonDB/horzion)
2023-04-11 02:16:51 +0000td_(~td@i53870914.versanet.de) (Ping timeout: 268 seconds)
2023-04-11 02:18:21 +0000td_(~td@i5387091F.versanet.de)
2023-04-11 04:35:27 +0000catman(~catman@user/catman) (Ping timeout: 255 seconds)
2023-04-11 04:51:40 +0000lordhorzion(~horzion@ProtonDB/horzion) (Ping timeout: 276 seconds)
2023-04-11 05:10:45 +0000Forkk(~forkk@li926-228.members.linode.com) (Ping timeout: 268 seconds)
2023-04-11 05:17:08 +0000horzion(~horzion@ProtonDB/horzion)
2023-04-11 05:30:51 +0000horzion(~horzion@ProtonDB/horzion) (Ping timeout: 250 seconds)
2023-04-11 05:37:31 +0000Forkk(~forkk@li926-228.members.linode.com)
2023-04-11 05:39:16 +0000hopelessness[m](~hopelessn@2001:470:69fc:105::3:4043)
2023-04-11 05:54:06 +0000retropikzel(9d1a4f9f46@2604:bf00:561:2000::ce)
2023-04-11 06:38:48 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds)
2023-04-11 06:40:51 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-11 06:48:06 +0000 <hopelessness[m]> I want to use `HLS` for my config and I set up the `hie.yaml`... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/cb1f65ab55a4bb244bba1b216a7155a4d020…>)
2023-04-11 06:48:12 +0000 <hopelessness[m]> I'm using cabal
2023-04-11 07:42:08 +0000 <geekosaur> I ended up using a fully cabalized config; NLS doesn't use env files like we use with the simple cabal config
2023-04-11 07:42:41 +0000 <geekosaur> this requires a `build` file, but doesn't require a `hie.yaml`
2023-04-11 07:43:14 +0000 <geekosaur> https://github.com/geekosaur/xmonad.hs/tree/skkukuk
2023-04-11 07:44:06 +0000 <hopelessness[m]> hm ok, thank you
2023-04-11 07:44:08 +0000 <hopelessness[m]> I'll take a look at it
2023-04-11 07:45:41 +0000 <geekosaur> (the build file is the standard cabal-suggested one, https://github.com/xmonad/xmonad-contrib/blob/master/scripts/build/build-with-cabal.sh, only with a little added verbosity
2023-04-11 07:45:46 +0000 <geekosaur> )
2023-04-11 07:46:31 +0000 <hopelessness[m]> something icks me about this solution
2023-04-11 07:46:42 +0000 <hopelessness[m]> I'd have preferred if it worked "natively"
2023-04-11 07:51:05 +0000 <geekosaur> there's a conflict between that and not having xmonad pollute the whole system
2023-04-11 07:51:20 +0000 <hopelessness[m]> mhm, I understand
2023-04-11 07:51:36 +0000 <hopelessness[m]> there's also the source-in-.config issue
2023-04-11 07:54:40 +0000cfricke(~cfricke@user/cfricke)
2023-04-11 07:57:36 +0000 <geekosaur> there's at least one window manager that is configured with lua, do you have the same problem with that?
2023-04-11 07:58:03 +0000 <hopelessness[m]> I haven't worked with awesomewm
2023-04-11 07:58:18 +0000 <hopelessness[m]> but I am quite fond of xmonad, it's a great wm
2023-04-11 09:00:07 +0000HAL[m](~evadk8mat@2001:470:69fc:105::3ed0) (Quit: You have been kicked for being idle)
2023-04-11 09:00:10 +0000liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-11 09:00:10 +0000unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-04-11 09:44:43 +0000ft(~ft@p4fc2a88b.dip0.t-ipconnect.de) (Quit: leaving)
2023-04-11 09:58:53 +0000Guest191(~Guest19@2404:130:0:1000:5484:a8db:f032:5999) (Ping timeout: 260 seconds)
2023-04-11 09:59:58 +0000hightower3(~hightower@213.149.51.164)
2023-04-11 10:03:01 +0000hightower2(~hightower@213.149.51.70) (Ping timeout: 276 seconds)
2023-04-11 10:26:25 +0000 <hopelessness[m]> I've got the config working but now the process is causing me a headache
2023-04-11 10:26:33 +0000 <hopelessness[m]> starting `xmonad` via the `xsession` desktop entry just .. doesn't work
2023-04-11 10:27:42 +0000 <hopelessness[m]> if I manually use `.cabal/bin/xmonad` or `.cache/xmonad/xmonad-x86_64-linux` then recompilation doesn't work and it tells me that `xmonad` is not on path
2023-04-11 10:28:02 +0000 <hopelessness[m]> but doing which xmonad gives me the cabal one
2023-04-11 10:28:09 +0000 <hopelessness[m]> which is the right binary and why are there so many
2023-04-11 11:30:55 +0000cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-04-11 11:43:34 +0000hightower3(~hightower@213.149.51.164) (Remote host closed the connection)
2023-04-11 13:14:44 +0000malook(~Thunderbi@2a02:9b0:404d:cde1:b870:daa7:7dc9:c378)
2023-04-11 13:24:17 +0000malook(~Thunderbi@2a02:9b0:404d:cde1:b870:daa7:7dc9:c378) (Remote host closed the connection)
2023-04-11 13:26:35 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 248 seconds)
2023-04-11 14:08:18 +0000cfricke(~cfricke@user/cfricke)
2023-04-11 14:10:36 +0000 <geekosaur> okay, the problem there is that the path in your terminal is not the same as the path in the display manager, unless you're on Fedora
2023-04-11 14:10:55 +0000liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-11 14:11:11 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-11 14:12:20 +0000 <geekosaur> I used to use a wrapper script (see `start-xmonad` in my config dir) but now I add it to the session startup (see `10profile` but you'll need to edit it because I have my dotfiles broken up into parts and pointed it to the `$PATH` part)
2023-04-11 14:12:28 +0000 <geekosaur> hopelessness[m] ^^
2023-04-11 14:14:11 +0000 <geekosaur> the `10profile` is symlinked to `/etc/X11/Xsession.d/10profile` but that's on debian/ubuntu, it may differ on other distributions
2023-04-11 14:16:02 +0000 <hopelessness[m]> ok, so `~/.local/bin/xmonad` is the "right" binary?
2023-04-11 14:16:21 +0000 <geekosaur> yes
2023-04-11 14:16:56 +0000 <geekosaur> and ~/.local/bin should be on your PATH
2023-04-11 14:17:26 +0000 <hopelessness[m]> ok cool
2023-04-11 14:18:59 +0000 <hopelessness[m]> thank you
2023-04-11 14:19:54 +0000 <geekosaur> my 10profile references `~/.bsa-common` which is the common part of both interactive (ssh or console) and non-interactive (X11 session) logins; if you really care it's at https://github.com/geekosaur/dotty/blob/master/.bsa-common but it's a lot more complex than most people need to care about 🙂
2023-04-11 14:24:36 +0000 <geekosaur> (most people don't even need to distinguish between console, ssh, screen/tmux, display manager…)
2023-04-11 15:10:42 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-04-11 15:30:04 +0000catman(~catman@user/catman)
2023-04-11 15:36:27 +0000 <hopelessness[m]> ok, something is off
2023-04-11 15:37:01 +0000 <hopelessness[m]> .local/bin/xmonad is not where the binary goes
2023-04-11 15:37:14 +0000 <hopelessness[m]> wait let me check something
2023-04-11 15:39:15 +0000catman(~catman@user/catman) (Ping timeout: 250 seconds)
2023-04-11 15:44:50 +0000 <hopelessness[m]> cabal build only places binaries in the .config/xmonad/dist-newstyle directory
2023-04-11 15:45:09 +0000 <hopelessness[m]> I think it's supposed to symlink the other binaries
2023-04-11 15:47:58 +0000 <geekosaur> yes, cabal build is only in-place. you want cabal install
2023-04-11 15:52:50 +0000 <hopelessness[m]> thanks
2023-04-11 15:53:06 +0000 <hopelessness[m]> now recompilation doesn't work because it uses `ghc` instead of cabal
2023-04-11 15:53:24 +0000 <hopelessness[m]> it says it does that because the `build` file doesn't exist
2023-04-11 16:00:12 +0000unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-04-11 16:00:12 +0000liskin[m](~liskinmat@2001:470:69fc:105::768) (Quit: You have been kicked for being idle)
2023-04-11 16:02:28 +0000 <geekosaur> right, you need ~/.config/xmonad/build (make sure to make it executable) for it to use anything other than ghc
2023-04-11 16:02:41 +0000liskin[m](~liskinmat@2001:470:69fc:105::768)
2023-04-11 16:02:56 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2023-04-11 16:03:18 +0000 <geekosaur> (well, if it sees a stack.yaml it does `stack exec ghc`, but there's no good equivalent for cabal)
2023-04-11 16:03:39 +0000 <hopelessness[m]> mhm
2023-04-11 16:03:48 +0000 <hopelessness[m]> can I just put that in the build
2023-04-11 16:03:52 +0000 <hopelessness[m]> the stack install?
2023-04-11 16:05:15 +0000 <geekosaur> I thought you were using cabal? you can't really switch that easily
2023-04-11 16:05:28 +0000 <hopelessness[m]> cabal install*
2023-04-11 16:05:31 +0000 <hopelessness[m]> I meant
2023-04-11 16:06:19 +0000 <geekosaur> you need to do a little more because building your config wants the result in a different place than cabal (or stack) puts it
2023-04-11 16:06:49 +0000 <geekosaur> so you need to use https://github.com/xmonad/xmonad-contrib/blob/master/scripts/build/build-with-cabal.sh
2023-04-11 16:06:57 +0000 <hopelessness[m]> I think it would have been easier going with stack from the get-go, lol
2023-04-11 16:07:06 +0000 <geekosaur> and there's an equivalent for stack because it doesn't put the result in the right place either
2023-04-11 16:07:38 +0000 <geekosaur> stack still wouldn't have given you HLS ability without doing the same extra work including a build script
2023-04-11 16:07:50 +0000 <geekosaur> HLS just doesn't know to follow the same things xmonad does
2023-04-11 16:08:18 +0000 <hopelessness[m]> alright
2023-04-11 16:08:48 +0000 <geekosaur> in fact, last I heard HLS got really confused if you have a simplified `stack.yaml` like `INSTALL.html` has you do
2023-04-11 16:10:53 +0000 <hopelessness[m]> `cd: can't cd to ~/.config/xmonad/`
2023-04-11 16:10:55 +0000 <hopelessness[m]> whyyyyyy?
2023-04-11 16:11:30 +0000 <hopelessness[m]> nvm
2023-04-11 16:11:51 +0000 <hopelessness[m]> it still doesn't replace itself
2023-04-11 16:13:25 +0000 <geekosaur> doesn't replace what?
2023-04-11 16:13:46 +0000 <geekosaur> ~/.cabal/bin/xmonad doesn't change; that came from `cabal install xmonad`
2023-04-11 16:15:07 +0000 <geekosaur> what changes is a file named something like `~/.cache/xmonad/xmonad-x86_64-linux` (will vary by OS and arch)
2023-04-11 16:24:28 +0000 <hopelessness[m]> wait, I'm mistaking something
2023-04-11 16:27:39 +0000 <hopelessness[m]> yeah, I mean the `xmonad --restart``
2023-04-11 16:27:57 +0000 <hopelessness[m]> s/``/`/
2023-04-11 16:27:57 +0000 <hopelessness[m]> It's not actually replacing itself
2023-04-11 16:28:59 +0000 <geekosaur> what's it doing?
2023-04-11 16:31:13 +0000 <hopelessness[m]> nothing apparently
2023-04-11 16:31:27 +0000 <hopelessness[m]> no error and no restart
2023-04-11 16:32:38 +0000 <geekosaur> oh, --restart without a recompile won't do much of anything visible. you need `xmonad --recompile` before it, and only bother to `--restart` if it succeeded
2023-04-11 16:35:32 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-04-11 16:35:55 +0000 <hopelessness[m]> I know, still the same
2023-04-11 16:35:58 +0000 <geekosaur> also, if all you change is a parameter to a layout, nothing visible will happen because xmonad doesn't want to lose your currently selected layout or any changes you've made via keys (number of master windows or position of the master/slave divider, usually)
2023-04-11 16:36:13 +0000 <geekosaur> you need mod-shift-space in that case to reset the layout
2023-04-11 16:36:32 +0000 <hopelessness[m]> I added a keybind with an xmessage spawn
2023-04-11 16:42:37 +0000catman(~catman@user/catman)
2023-04-11 17:04:09 +0000 <geekosaur> beh. I just had xmonad die on a getWindowAttributes that wasn't wrapped in a userCode
2023-04-11 17:19:53 +0000cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-04-11 17:35:47 +0000catman(~catman@user/catman) (Quit: WeeChat 3.8)
2023-04-11 18:00:51 +0000hightower2(~hightower@213.149.61.192)
2023-04-11 19:55:27 +0000ft(~ft@p4fc2a88b.dip0.t-ipconnect.de)
2023-04-11 21:40:21 +0000evie_kurt001[m](~eviekurt0@2001:470:69fc:105::3:434e)
2023-04-11 22:48:37 +0000catman(~catman@user/catman)
2023-04-11 23:04:37 +0000evie_kurt001[m](~eviekurt0@2001:470:69fc:105::3:434e) (Quit: User was banned)
2023-04-11 23:35:02 +0000catman(~catman@user/catman) (Ping timeout: 265 seconds)