2023/06/01

2023-06-01 00:24:08 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 00:25:45 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 00:26:05 +0200horzion(~horzion@ProtonDB/horzion)
2023-06-01 00:45:58 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 00:46:23 +0200scrungus(~scrungus@bras-base-aurron9127w-grc-46-70-31-27-241.dsl.bell.ca) (Quit: WeeChat 3.8)
2023-06-01 01:52:07 +0200mncheck(~mncheck@193.224.205.254) (Ping timeout: 240 seconds)
2023-06-01 02:13:37 +0200blue-velvet[m](~kobalinus@2001:470:69fc:105::f8eb)
2023-06-01 02:13:37 +0200jish[m](~jbggsmatr@2001:470:69fc:105::2:995f)
2023-06-01 02:13:37 +0200mc47[m](~mc47matri@2001:470:69fc:105::733)
2023-06-01 03:11:18 +0200horzion(~horzion@ProtonDB/horzion) (Quit: Off praying to the Omnissiah)
2023-06-01 03:36:10 +0200nasrudin__(~nasrudin_@2600:381:a92c:bfec:3d54:17f:e28c:6712)
2023-06-01 03:43:10 +0200Guest52(~Guest52@2600:387:15:131b::1)
2023-06-01 03:43:22 +0200nasrudin__(~nasrudin_@2600:381:a92c:bfec:3d54:17f:e28c:6712) (Quit: Leaving)
2023-06-01 03:44:28 +0200 <Guest52> got a question about XMonad.Layout.SubLayouts
2023-06-01 03:45:13 +0200 <Guest52> basically I want to write a function to send all windows in the sublayout group with the currently focused window to another workspace
2023-06-01 03:45:14 +0200unclechu(~unclechu@2001:470:69fc:105::354)
2023-06-01 03:45:53 +0200 <Guest52> https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Layout-SubLayouts.html#v:onG…
2023-06-01 03:45:57 +0200 <Guest52> kinda looks right
2023-06-01 03:46:13 +0200 <Guest52> except all the functions I can think of using to do this are impure
2023-06-01 03:46:43 +0200 <Guest52> the other direction I can think of would be to use SubMessage
2023-06-01 03:47:38 +0200 <Guest52> but I don't really understand what https://hackage.haskell.org/package/xmonad-contrib-0.17.1/docs/XMonad-Config-Prime.html#t:SomeMess… is or what you can do with it
2023-06-01 03:48:47 +0200 <Guest52> Anyone have a suggestion for an example config (or docs or forum threads) explaining what you can do with Messages?
2023-06-01 03:55:34 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-06-01 04:46:54 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 04:47:05 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 04:57:29 +0200td_(~td@i53870935.versanet.de) (Ping timeout: 250 seconds)
2023-06-01 04:59:31 +0200td_(~td@i5387091E.versanet.de)
2023-06-01 05:45:59 +0200haasn`(~nand@haasn.dev)
2023-06-01 05:50:10 +0200Guest52(~Guest52@2600:387:15:131b::1) (Quit: Client closed)
2023-06-01 06:13:14 +0200[Leary](~Leary]@user/Leary/x-0910699) (Remote host closed the connection)
2023-06-01 06:21:21 +0200[Leary](~Leary]@user/Leary/x-0910699)
2023-06-01 07:23:16 +0200chomwitt(~chomwitt@2a02:587:7a16:6700:1ac0:4dff:fedb:a3f1)
2023-06-01 07:24:59 +0200Guest52(~Guest52@ip72-197-77-4.sd.sd.cox.net)
2023-06-01 07:35:51 +0200Maeda(~Maeda@91-161-10-149.subs.proxad.net)
2023-06-01 08:00:02 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 265 seconds)
2023-06-01 08:01:49 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2023-06-01 08:11:29 +0200mncheck(~mncheck@193.224.205.254)
2023-06-01 08:26:47 +0200Guest52(~Guest52@ip72-197-77-4.sd.sd.cox.net) (Quit: Client closed)
2023-06-01 08:47:25 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 08:47:41 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 09:36:05 +0200mc47(~mc47@xmonad/TheMC47)
2023-06-01 09:40:45 +0200Maeda(~Maeda@91-161-10-149.subs.proxad.net) (Quit: leaving)
2023-06-01 09:42:12 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 10:12:48 +0200cfricke(~cfricke@user/cfricke)
2023-06-01 10:51:31 +0200m5zs7k(aquares@web10.mydevil.net) (Ping timeout: 240 seconds)
2023-06-01 10:52:11 +0200m5zs7k(aquares@web10.mydevil.net)
2023-06-01 11:20:09 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 11:38:30 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 11:43:01 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 11:46:18 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 11:49:37 +0200chomwitt(~chomwitt@2a02:587:7a16:6700:1ac0:4dff:fedb:a3f1) (Ping timeout: 265 seconds)
2023-06-01 11:54:07 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 11:57:22 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 12:00:01 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 12:09:11 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de) (Quit: leaving)
2023-06-01 12:19:20 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 12:23:25 +0200mc47(~mc47@xmonad/TheMC47) (Remote host closed the connection)
2023-06-01 12:23:48 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 12:23:48 +0200_qw(~eqw@31.134.178.99) (Ping timeout: 240 seconds)
2023-06-01 12:26:07 +0200_qw(~eqw@31.134.178.99)
2023-06-01 12:41:07 +0200_qw(~eqw@31.134.178.99) (Ping timeout: 240 seconds)
2023-06-01 12:41:59 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 12:44:07 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 13:00:45 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 13:02:52 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 13:13:39 +0200_qw(~eqw@31.134.178.99)
2023-06-01 13:51:54 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 13:51:57 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 14:02:30 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 14:08:25 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 14:10:24 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 14:16:02 +0200redgloboli(~redglobol@user/redgloboli) (Quit: ...enter the matrix...)
2023-06-01 14:16:30 +0200redgloboli(~redglobol@user/redgloboli)
2023-06-01 14:16:37 +0200redgloboli(~redglobol@user/redgloboli) (Remote host closed the connection)
2023-06-01 14:17:45 +0200redgloboli(~redglobol@user/redgloboli)
2023-06-01 14:31:40 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 15:08:40 +0200chomwitt(~chomwitt@ppp-94-67-203-168.home.otenet.gr)
2023-06-01 15:59:31 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 15:59:41 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 16:10:20 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 16:13:52 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 16:50:58 +0200cfricke(~cfricke@user/cfricke) (Quit: WeeChat 3.8)
2023-06-01 16:52:20 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 16:52:31 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 16:59:04 +0200thunderrd(~thunderrd@183.182.110.206) (Remote host closed the connection)
2023-06-01 17:26:58 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2023-06-01 17:41:03 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 17:41:05 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 17:50:21 +0200deepy(deepy@user/deepy)
2023-06-01 17:54:17 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 17:56:09 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 18:02:08 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 18:13:28 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 18:15:55 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 18:18:38 +0200hightower3(~hightower@cm-2185.cable.globalnet.hr)
2023-06-01 18:21:07 +0200hightower2(~hightower@213.149.61.64) (Ping timeout: 240 seconds)
2023-06-01 18:29:14 +0200scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Quit: leaving)
2023-06-01 18:29:15 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 18:48:01 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 18:53:09 +0200scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2023-06-01 19:01:07 +0200scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 240 seconds)
2023-06-01 19:03:17 +0200scardinal(~supreme@87.61.100.169)
2023-06-01 19:25:40 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 19:32:49 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 19:34:44 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 19:53:19 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 19:58:07 +0200vanvik(~vanvik@78.156.11.181)
2023-06-01 19:59:29 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 20:04:35 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 20:05:15 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 20:07:44 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 20:26:39 +0200 <dminuoso> Mmm. So Im using xmonad from nixos. Ive been pondering a bit about the environment.
2023-06-01 20:27:13 +0200 <dminuoso> My question is: How do I control PATH for the purpose of calling some external program via `spawn`
2023-06-01 21:48:28 +0200ft(~ft@p4fc2a88b.dip0.t-ipconnect.de)
2023-06-01 22:01:06 +0200 <[Leary]> dminuoso: I think the NixOS way would be to either nixify the program and include it in an active profile, or invoke the binary with its full path. But if you do want to mess with PATH directly, one of .bash_profile, .zprofile, etc probably works. Otherwise, you can use `getEnv` and `setEnv` before `xmonad` in your config `main`. If you want to isolate the change to `spawn`, you can write your own variant like `mySpawn c = spawn ("PATH=\"/path/to/my/b
2023-06-01 22:01:06 +0200 <[Leary]> ins:$PATH\"; " ++ c)`.
2023-06-01 22:04:53 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 22:24:29 +0200 <geekosaur> isn't home-manager supposed to deal with this for you?
2023-06-01 22:24:44 +0200geekosaurdoesn't know that much about nixos
2023-06-01 22:25:37 +0200 <geekosaur> personally I dropped it into the standard X session, but (a) single-user hack (b) for debian/ubuntu only
2023-06-01 22:27:30 +0200chomwitt(~chomwitt@ppp-94-67-203-168.home.otenet.gr) (Remote host closed the connection)
2023-06-01 22:39:25 +0200Guest52(~Guest52@2001:579:e224:17:b293:446e:deac:2f99)
2023-06-01 22:41:36 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 22:44:24 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)
2023-06-01 22:45:22 +0200 <Guest52>  @ dminuoso - to add to the options [Leary] mentioned
2023-06-01 22:46:26 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 22:47:19 +0200 <Guest52> if you aren't using home manager, would prefer to change the system-wide path, or just want something that will work for the time being
2023-06-01 22:47:38 +0200 <Guest52> you could put in your configuration.nix something like
2023-06-01 22:48:03 +0200 <Guest52> ```
2023-06-01 22:48:03 +0200 <Guest52> environment.shellInit = ''
2023-06-01 22:48:04 +0200 <Guest52>     export PATH=$PATH:/home/dminuoso/your/path/here
2023-06-01 22:48:04 +0200 <Guest52>   '';
2023-06-01 22:48:05 +0200 <Guest52> ```
2023-06-01 22:49:22 +0200 <Guest52> depending on how you have xmonad installed and configured, this may also be the path of least resistance
2023-06-01 23:26:42 +0200yaslam0(~yaslam0@user/yaslam) (Quit: -a- Connection Timed Out)
2023-06-01 23:26:54 +0200yaslam0(~yaslam0@user/yaslam)
2023-06-01 23:57:29 +0200yaslam0(~yaslam0@user/yaslam) (Read error: Connection reset by peer)