2023/01/22

2023-01-22 00:00:04 +0000 <trevdev[m]> dmenuRun m = safeSpawn "dmenu_run" $ baseMenuFlags ++ menuSelectBg "#ABDC88" ++ verticalMenu "10"
2023-01-22 00:01:58 +0000 <geekosaur[m]> what's m for?
2023-01-22 00:02:22 +0000 <trevdev[m]> Probably not required, it's rot
2023-01-22 00:04:09 +0000 <trevdev[m]> Actually no, "ambiguous type variable m0 arrising from safeSpawn"
2023-01-22 00:04:10 +0000 <trevdev[m]> It does something
2023-01-22 00:04:18 +0000 <trevdev[m]> Or is supposed to
2023-01-22 00:06:17 +0000 <geekosaur[m]> I'm not sure that's related; it sounds more like safeSpawn can't figure out what MonadIO instance to use. but if you're calling it in a keybinding, it should know to use X
2023-01-22 00:10:16 +0000 <geekosaur[m]> oh, I see. without either it or a type signature, the monomorphism restriction bites you
2023-01-22 00:10:24 +0000 <geekosaur[m]> I'd just add a type signature
2023-01-22 00:11:18 +0000 <geekosaur[m]> `dmenuRun :: MonadIO m => m ()`
2023-01-22 00:12:12 +0000 <geekosaur[m]> or dmenuRun :: X ()
2023-01-22 00:26:33 +0000ghormoon(~ghormoon@ghorland.net) (Ping timeout: 252 seconds)
2023-01-22 01:03:26 +0000ghormoon(~ghormoon@ghorland.net)
2023-01-22 01:07:15 +0000 <trevdev[m]> I'll give it a shot when I get home. Thanks geekosaur @geekosaur:matrix.org: !
2023-01-22 03:03:31 +0000banc(banc@gateway/vpn/protonvpn/banc) (Ping timeout: 268 seconds)
2023-01-22 03:24:12 +0000banc(banc@gateway/vpn/protonvpn/banc)
2023-01-22 03:38:04 +0000 <HB[m]> Hi guys, how's everyone doing? 🙂
2023-01-22 03:39:00 +0000 <HB[m]> I'm having a bit of trouble building xmobar with stack, latest version.
2023-01-22 03:39:01 +0000 <HB[m]> I pull the git repo in ~/.config/xmonad/xmobar and add -xmobar in my stack.yml and then stack build and I get errors
2023-01-22 03:41:39 +0000terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::) (Quit: The Lounge - https://thelounge.chat)
2023-01-22 03:43:47 +0000 <HB[m]> * I'm having a bit of trouble building xmobar with stack, latest version.
2023-01-22 03:43:47 +0000 <HB[m]> I pull the git repo in ~/.config/xmonad/xmobar and add -xmobar in my stack.yml and then stack build and I get errors.
2023-01-22 03:43:47 +0000 <HB[m]> Oh, nm. Git repo moved.
2023-01-22 03:43:55 +0000terrorjack(~terrorjac@2a01:4f8:1c1e:4e8c::)
2023-01-22 03:51:14 +0000td_(~td@83.135.9.44) (Ping timeout: 260 seconds)
2023-01-22 03:52:51 +0000td_(~td@83.135.9.13)
2023-01-22 04:07:09 +0000abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-01-22 04:09:03 +0000 <HB[m]> * I'm having a bit of trouble building xmobar with stack, latest version.
2023-01-22 04:09:03 +0000 <HB[m]> I pull the git repo in ~/.config/xmonad/xmobar and add -xmobar in my stack.yml and then stack build and I get errors.
2023-01-22 04:09:03 +0000 <HB[m]> Oh, nm. Git repo moved.
2023-01-22 04:09:03 +0000 <HB[m]> Changed to the new font format. xmobar is no longer from ubuntu repos.
2023-01-22 04:15:07 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 248 seconds)
2023-01-22 04:20:21 +0000 <trevdev[m]> <geekosaur[m]> "I'd just add a type signature" <- Ok wow, so explicitly adding a signature rather than inferring it made the difference. No need for `m`, nor to call the function in the XMonad config. The results at runtime are the same. Fascinating to see how one detail can change the shape of the linter's expectations
2023-01-22 04:21:03 +0000 <trevdev[m]> O perhaps even the behavior of the code ??
2023-01-22 04:21:15 +0000 <trevdev[m]> s/O/Or/, s/behavior/behaviour/
2023-01-22 04:56:14 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net) (Ping timeout: 272 seconds)
2023-01-22 06:20:10 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds)
2023-01-22 06:25:59 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-01-22 06:26:56 +0000abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 256 seconds)
2023-01-22 07:06:55 +0000ElKowar7(~ElKowar@srv-fin.xware-gmbh.de)
2023-01-22 07:09:21 +0000Forkk_(~forkk@li926-228.members.linode.com)
2023-01-22 07:10:13 +0000td__(~td@83.135.9.13)
2023-01-22 07:11:36 +0000gauge_(~gauge@user/gauge)
2023-01-22 07:14:55 +0000td_(~td@83.135.9.13) (*.net *.split)
2023-01-22 07:14:55 +0000xmonadtrack(~xmonadtra@xmonad/geekosaur) (*.net *.split)
2023-01-22 07:14:56 +0000Solitary(~Solitary@user/solitary) (*.net *.split)
2023-01-22 07:14:56 +0000Forkk(~forkk@li926-228.members.linode.com) (*.net *.split)
2023-01-22 07:14:56 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de) (*.net *.split)
2023-01-22 07:14:56 +0000gauge(~gauge@user/gauge) (*.net *.split)
2023-01-22 07:14:56 +0000byorgey(~byorgey@155.138.238.211) (*.net *.split)
2023-01-22 07:14:56 +0000ElKowar(~ElKowar@srv-fin.xware-gmbh.de) (*.net *.split)
2023-01-22 07:15:03 +0000ElKowar7ElKowar
2023-01-22 07:19:45 +0000byorgey(~byorgey@155.138.238.211)
2023-01-22 07:20:03 +0000xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com)
2023-01-22 07:20:04 +0000xmonadtrack(~xmonadtra@069-135-003-034.biz.spectrum.com) (Changing host)
2023-01-22 07:20:04 +0000xmonadtrack(~xmonadtra@xmonad/geekosaur)
2023-01-22 07:21:20 +0000wz1000(~zubin@static.11.113.47.78.clients.your-server.de)
2023-01-22 07:21:27 +0000 <geekosaur[m]> look up the monomorphism restriction
2023-01-22 07:23:37 +0000Solitary(~Solitary@user/solitary)
2023-01-22 07:35:45 +0000qbt(~qbt@user/edun)
2023-01-22 07:36:04 +0000qbt(~qbt@user/edun) (Client Quit)
2023-01-22 11:30:50 +0000haskl(~haskl@user/haskl) (Read error: Connection reset by peer)
2023-01-22 11:32:39 +0000haskl(~haskl@user/haskl)
2023-01-22 11:51:27 +0000Solitary(~Solitary@user/solitary) (Quit: All work and no play makes Jack a dull boy.)
2023-01-22 11:55:09 +0000Solitary(~Solitary@user/solitary)
2023-01-22 12:46:43 +0000tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl)
2023-01-22 13:05:06 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-22 13:19:55 +0000yaslam(~yaslam@user/yaslam) (Remote host closed the connection)
2023-01-22 13:20:19 +0000yaslam(~yaslam@user/yaslam)
2023-01-22 13:35:55 +0000Digit(~user@user/digit) (Read error: Connection reset by peer)
2023-01-22 13:40:34 +0000Digit(~user@user/digit)
2023-01-22 13:51:39 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 248 seconds)
2023-01-22 14:24:52 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-22 15:30:31 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 260 seconds)
2023-01-22 15:34:03 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-22 15:52:47 +0000 <trevdev[m]> Turns out I had some caching going on and my functions linted fine but didn't actually work. I think I am learning that xmonad on nixos is weird.
2023-01-22 15:54:28 +0000 <trevdev[m]> I moved my modules to the .config/xmonad/lib folder instead of just the same folder as xmonad.hs. Pretty sure they're picked up now but the haskell-language-server can't figure out where they are now
2023-01-22 15:55:43 +0000 <trevdev[m]> Reading suggests using (and learning) stack may fix that, but that would defeat the purpose of using nixos in the first place so I am not really able to trust the language server atm
2023-01-22 16:00:08 +0000unclechu(~unclechu@2001:470:69fc:105::354) (Quit: You have been kicked for being idle)
2023-01-22 16:09:12 +0000 <[Leary]> trevdev[m]: It's low-tech compared to HLS, but on my NixOS setup I use ghcid via alias ghcidx='ghcid --command "$XMONAD_GHC"i" -i$HOME/.config/xmonad/lib -Wall $HOME/.config/xmonad/xmonad.hs"'
2023-01-22 16:09:26 +0000unclechu(~unclechu@2001:470:69fc:105::354)
2023-01-22 16:12:01 +0000 <[Leary]> If you really want to use HLS, you probably just need a cabal file to help it understand the structure of the project (telling it that xmonad.hs is Main and lib is your source dir, etc). But I don't use it myself, so don't quote me on that.
2023-01-22 16:52:37 +0000 <trevdev[m]> From a learning standpoint the LSP is a valuable tool. HLS in particular has taught me things that I probably would not have looked up!
2023-01-22 16:53:43 +0000 <trevdev[m]> I don't know how to configure Cabal and if it involves declaring literally everything down to where xmonad/contrib are on nix then its a whole thing
2023-01-22 16:58:47 +0000gknux(~gknux@user/galaxy-knuckles/x-3015990) (Quit: ....and i am outta here....)
2023-01-22 17:00:28 +0000gknux(~gknux@user/galaxy-knuckles/x-3015990)
2023-01-22 17:01:40 +0000jao(~jao@cpc103048-sgyl39-2-0-cust502.18-2.cable.virginm.net)
2023-01-22 17:02:32 +0000 <[Leary]> I haven't tried, but in a `cabal.project` file you could set `with-compiler` to the value of $XMONAD_GHC. That should make the versions of xmonad and xmonad-contrib you're using available, such that cabal prefers them over fetching and building different versions from hackage.
2023-01-22 17:05:33 +0000gknux(~gknux@user/galaxy-knuckles/x-3015990) (Quit: ....and i am outta here....)
2023-01-22 17:08:17 +0000gknux(~gknux@user/galaxy-knuckles/x-3015990)
2023-01-22 17:08:39 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 265 seconds)
2023-01-22 17:23:32 +0000 <trevdev[m]> I'll give it a shot later, thanks!
2023-01-22 18:04:56 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-22 18:23:57 +0000escobear(~gknux@user/galaxy-knuckles/x-3015990)
2023-01-22 18:24:08 +0000gknux(~gknux@user/galaxy-knuckles/x-3015990) (Ping timeout: 260 seconds)
2023-01-22 18:24:49 +0000escobeargknux
2023-01-22 20:34:19 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb) (Ping timeout: 260 seconds)
2023-01-22 20:46:36 +0000rundown(~defjam@2a02:c7e:2807:b900:6c7a:2207:d06b:87cb)
2023-01-22 20:50:46 +0000abhixec(~abhinav@c-67-169-139-16.hsd1.ca.comcast.net)
2023-01-22 21:00:51 +0000yaslam(~yaslam@user/yaslam) (Quit: ZNC 1.8.2 - https://znc.in)
2023-01-22 21:01:35 +0000yaslam(~yaslam@user/yaslam)
2023-01-22 23:46:54 +0000 <trevdev[m]> So I gave up on createProcess and XMonad.Util.Run and fully regressed back into just concatenating strings for keybinding shell commands. I wanted a way to use the same color for my theme in my dmenu scripts as I do in everything else. My original issue was "if cli args for dmenu need to be wrapped in single quotes, but menuArgs require that they do not, how do I use the same colors for both?" Well in my case, the answer is, "you don't"
2023-01-22 23:46:54 +0000 <trevdev[m]> https://paste.debian.net/1268166/
2023-01-22 23:48:12 +0000 <trevdev[m]> At least I mapped the same data versus 2 different variables. I think this is cleaner
2023-01-22 23:51:09 +0000 <geekosaur> cli args should be find with double quotes unless they include dollar signs, in which case `show` may be a cheaty way to get what you want
2023-01-22 23:51:22 +0000tremon(~tremon@83-85-213-108.cable.dynamic.v4.ziggo.nl) (Quit: getting boxed in)
2023-01-22 23:56:19 +0000 <geekosaur> > text "#32af4b"
2023-01-22 23:56:21 +0000 <lambdabot> #32af4b
2023-01-22 23:56:29 +0000 <geekosaur> > text $ show "#32af4b"
2023-01-22 23:56:31 +0000 <lambdabot> "#32af4b"
2023-01-22 23:56:46 +0000 <geekosaur> (`text` is a lambdabot-ism)