IRCBrowse

2021/10/03

2021-10-03 02:04:34 +0000banc(banc@gateway/vpn/airvpn/banc) (Ping timeout: 252 seconds)
2021-10-03 02:22:01 +0000banc(banc@gateway/vpn/airvpn/banc)
2021-10-03 02:36:53 +0000minty(~minty@pool-173-61-191-195.cmdnnj.fios.verizon.net)
2021-10-03 02:37:17 +0000minty(~minty@pool-173-61-191-195.cmdnnj.fios.verizon.net) (Client Quit)
2021-10-03 02:38:33 +0000SpiderPig(~matt@107.117.203.177)
2021-10-03 02:39:01 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Remote host closed the connection)
2021-10-03 02:41:35 +0000terrorjack(~terrorjac@static.3.200.12.49.clients.your-server.de) (Quit: The Lounge - https://thelounge.chat)
2021-10-03 02:43:48 +0000terrorjack(~terrorjac@static.3.200.12.49.clients.your-server.de)
2021-10-03 02:50:43 +0000SpiderPig(~matt@107.117.203.177) (Ping timeout: 252 seconds)
2021-10-03 03:00:04 +0000td_(~td@94.134.91.111) (Ping timeout: 252 seconds)
2021-10-03 03:01:51 +0000td_(~td@muedsl-82-207-238-036.citykom.de)
2021-10-03 03:16:22 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)
2021-10-03 03:52:44 +0000trillp(~trillp@69.233.98.238)
2021-10-03 04:15:18 +0000Buliarou1(~gypsydang@185.207.166.57)
2021-10-03 04:15:32 +0000incertia_(~incertia@d4-50-26-103.nap.wideopenwest.com)
2021-10-03 04:15:57 +0000nomadxx3(~lanomadx@69.167.45.89)
2021-10-03 04:16:25 +0000skewerr(spoonm@inaba.spoonm.org)
2021-10-03 04:16:31 +0000matijja`(~matijja@193.77.181.201)
2021-10-03 04:16:35 +0000joshproehl_(~quassel@user/joshproehl)
2021-10-03 04:16:44 +0000electr0n_(~electr0n@about/security/founder/electr0n)
2021-10-03 04:17:08 +0000piele(~piele@tbonesteak.creativeserver.net)
2021-10-03 04:17:33 +0000slime__(~slime@lychee.hauntware.cc)
2021-10-03 04:20:21 +0000electr0n(~electr0n@about/security/founder/electr0n) (*.net *.split)
2021-10-03 04:20:21 +0000incertia(~incertia@d4-50-26-103.nap.wideopenwest.com) (*.net *.split)
2021-10-03 04:20:21 +0000piele_(~piele@tbonesteak.creativeserver.net) (*.net *.split)
2021-10-03 04:20:21 +0000slime_(~slime@lychee.hauntware.cc) (*.net *.split)
2021-10-03 04:20:21 +0000nomadxxxx3(~lanomadx@69.167.45.89) (*.net *.split)
2021-10-03 04:20:22 +0000matijja(~matijja@193.77.181.201) (*.net *.split)
2021-10-03 04:20:22 +0000joshproehl(~quassel@user/joshproehl) (*.net *.split)
2021-10-03 04:20:22 +0000spoonm(spoonm@inaba.spoonm.org) (*.net *.split)
2021-10-03 04:20:22 +0000Buliarous(~gypsydang@185.207.166.57) (*.net *.split)
2021-10-03 04:20:22 +0000incertia_incertia
2021-10-03 04:22:03 +0000piele(~piele@tbonesteak.creativeserver.net) (Ping timeout: 252 seconds)
2021-10-03 04:22:13 +0000piele(~piele@tbonesteak.creativeserver.net)
2021-10-03 04:24:03 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2021-10-03 04:24:03 +0000allbery_b(~geekosaur@xmonad/geekosaur)
2021-10-03 04:24:06 +0000allbery_bgeekosaur
2021-10-03 04:26:26 +0000haasn`(~nand@haasn.dev)
2021-10-03 04:26:41 +0000td__(~td@muedsl-82-207-238-036.citykom.de)
2021-10-03 04:27:24 +0000deebo_(~globe@stonebay32.com)
2021-10-03 04:27:41 +0000yosafbridge`(~yosafbrid@static.38.6.217.95.clients.your-server.de)
2021-10-03 04:27:51 +0000yosafbridge(~yosafbrid@static.38.6.217.95.clients.your-server.de) (Ping timeout: 252 seconds)
2021-10-03 04:27:52 +0000pl_(sid98063@id-98063.helmsley.irccloud.com)
2021-10-03 04:28:24 +0000td_(~td@muedsl-82-207-238-036.citykom.de) (Ping timeout: 252 seconds)
2021-10-03 04:28:24 +0000jokleinn(~jokleinn@user/jokleinn) (Ping timeout: 252 seconds)
2021-10-03 04:28:24 +0000deebo(~globe@stonebay32.com) (Ping timeout: 252 seconds)
2021-10-03 04:28:28 +0000haasn(~nand@haasn.dev) (Ping timeout: 252 seconds)
2021-10-03 04:28:28 +0000pl(sid98063@2a03:5180:f:1::1:7f0f) (Ping timeout: 252 seconds)
2021-10-03 04:28:28 +0000Nahra`(~user@static.161.95.99.88.clients.your-server.de) (Ping timeout: 252 seconds)
2021-10-03 04:28:28 +0000haasn`haasn
2021-10-03 04:28:28 +0000pl_pl
2021-10-03 04:28:53 +0000terrorjack1(~terrorjac@static.3.200.12.49.clients.your-server.de)
2021-10-03 04:29:13 +0000terrorjack(~terrorjac@static.3.200.12.49.clients.your-server.de) (Ping timeout: 252 seconds)
2021-10-03 04:29:13 +0000terrorjack1terrorjack
2021-10-03 04:29:46 +0000Forkk(~forkk@li926-228.members.linode.com) (Ping timeout: 252 seconds)
2021-10-03 04:29:48 +0000Nahra``(~user@static.161.95.99.88.clients.your-server.de)
2021-10-03 04:30:40 +0000Forkk(~forkk@li926-228.members.linode.com)
2021-10-03 04:30:45 +0000electr0n_electr0n
2021-10-03 04:33:23 +0000tv(~tv@user/tv) (Ping timeout: 252 seconds)
2021-10-03 04:33:31 +0000tv1(~tv@user/tv)
2021-10-03 04:36:16 +0000steve_(~steve@ool-182c2aa4.dyn.optonline.net)
2021-10-03 04:37:13 +0000steve__(~steve@ool-182c2aa4.dyn.optonline.net) (Read error: Connection reset by peer)
2021-10-03 04:38:08 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net) (Ping timeout: 252 seconds)
2021-10-03 04:38:21 +0000abhixec(~abhixec@c-67-169-139-16.hsd1.ca.comcast.net)
2021-10-03 04:41:25 +0000darkstardevx(~darkstard@2601:1c2:300:c8a0::f2b6) (Remote host closed the connection)
2021-10-03 04:41:25 +0000td__(~td@muedsl-82-207-238-036.citykom.de) (Ping timeout: 252 seconds)
2021-10-03 04:41:38 +0000td_(~td@muedsl-82-207-238-036.citykom.de)
2021-10-03 04:41:41 +0000terrorjack(~terrorjac@static.3.200.12.49.clients.your-server.de) (Read error: Connection reset by peer)
2021-10-03 04:41:44 +0000darkstardevx(~darkstard@2601:1c2:300:c8a0::f2b6)
2021-10-03 04:41:58 +0000scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk) (Ping timeout: 252 seconds)
2021-10-03 04:42:14 +0000terrorjack(~terrorjac@static.3.200.12.49.clients.your-server.de)
2021-10-03 04:42:24 +0000scardinal(~supreme@customer-212-237-101-39.ip4.gigabit.dk)
2021-10-03 04:44:46 +0000darkstarx(~darkstard@2601:1c2:300:c8a0::f2b6)
2021-10-03 04:46:49 +0000deepy(deepy@user/deepy) (Ping timeout: 252 seconds)
2021-10-03 04:47:55 +0000deepy(deepy@user/deepy)
2021-10-03 04:48:04 +0000darkstardevx(~darkstard@2601:1c2:300:c8a0::f2b6) (Ping timeout: 252 seconds)
2021-10-03 05:00:17 +0000jsoo_(~znc@irc.refl.club)
2021-10-03 05:02:02 +0000trillp_(~trillp@69.233.98.238)
2021-10-03 05:02:59 +0000trillp(~trillp@69.233.98.238) (Killed (NickServ (GHOST command used by trillp_)))
2021-10-03 05:03:31 +0000jsoo(~znc@irc.refl.club) (Ping timeout: 252 seconds)
2021-10-03 05:05:40 +0000trillp_(~trillp@69.233.98.238) (Client Quit)
2021-10-03 05:52:28 +0000 <Solid> <elonsroadster[m]> Thats not REQUIRED just for using xmonad though... << now I'm confused; weren't we talking about extra steps to take in order to facilitate the "modify contrib" workflow? I'm just saying that the extra step for stack is literally "do nothing", while it seems non-trivial with a nix-based setup
2021-10-03 06:42:34 +0000 <HAL[m]> hello, I deleted the `~/.stack` folder and reinstall packages in `~/.xmonad` folder, but with the following error:... (full message at https://libera.ems.host/_matrix/media/r0/download/libera.chat/55a958deecd2b10843631b7a531794189079…)
2021-10-03 06:46:44 +0000 <Solid> seems like it can't determine your system in order to install a proper ghc version
2021-10-03 06:47:09 +0000 <Solid> you could try changing the stack resolver to match your system GHC's and then force stack to use that
2021-10-03 06:57:38 +0000 <HAL[m]> <Solid> "seems like it can't determine..." <- Thanks this is the second time I forgot... checked #4711 and created the symlink `sudo ln -s /usr/lib/libncurses.so.6 /usr/lib/libtinfo.so.6`
2021-10-03 06:57:55 +0000 <Solid> ah yes, that also works
2021-10-03 07:12:47 +0000qbt(~qbt@user/edun) ()
2021-10-03 08:03:35 +0000coldpress(~coldpress@128.9.105.34.bc.googleusercontent.com)
2021-10-03 08:10:58 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Ping timeout: 252 seconds)
2021-10-03 08:17:33 +0000allbery_b(~geekosaur@xmonad/geekosaur)
2021-10-03 08:17:33 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2021-10-03 08:17:36 +0000allbery_bgeekosaur
2021-10-03 09:16:20 +0000seschwar(~seschwar@user/seschwar)
2021-10-03 09:51:17 +0000Solid[m](~slot-matr@2001:470:69fc:105::1:a84)
2021-10-03 10:48:19 +0000sagax(~sagax_nb@user/sagax)
2021-10-03 10:55:09 +0000cyr4x3(~cyr4x3@139.47.115.87)
2021-10-03 10:58:47 +0000Archanus[m](~archanusm@2001:470:69fc:105::f953)
2021-10-03 11:41:27 +0000allbery_b(~geekosaur@xmonad/geekosaur)
2021-10-03 11:41:27 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Killed (NickServ (GHOST command used by allbery_b)))
2021-10-03 11:41:30 +0000allbery_bgeekosaur
2021-10-03 11:51:43 +0000cyr4x3(~cyr4x3@139.47.115.87) (Quit: WeeChat 2.3)
2021-10-03 14:25:33 +0000Solidnotices that mid-October is merely two weeks away... :)
2021-10-03 14:26:17 +0000 <geekosaur> tempus fugit
2021-10-03 14:26:49 +0000 <geekosaur> we've missed so many deadlines already, what's another? :þ
2021-10-03 14:28:42 +0000 <Solid> Oct 25 would mark the one year anniversary of the "pls do another release soon" issue; probably best not to celebrate that :>
2021-10-03 14:29:07 +0000 <geekosaur> halloween?
2021-10-03 14:29:56 +0000 <Solid> A halloween-themed xmonad release? With pumpkins as decorations!
2021-10-03 14:33:20 +0000 <mc47[m]> Ouf, I couldn't help the temptation of going on an indulgent trip to Italy after doing the thesis defense
2021-10-03 14:34:15 +0000 <mc47[m]> Is there any issues I could work on? Otherwise I'd try and update the DynamicLog references
2021-10-03 14:39:59 +0000 <Solid> probably not even that much that still needs work, tbh; once we merge #605 only the EWMH stuff and possibly the extensible state non-unique keys remain
2021-10-03 14:40:33 +0000 <Solid> the former would be really nice to have, the latter seems like it could also wait until the next release
2021-10-03 14:41:04 +0000 <mc47[m]> Agreed
2021-10-03 14:41:36 +0000 <Solid> (and if all else fails I would also be in favour of delaying the EMWH stuff until the next release; better get something out than treading water for another 6 months :))
2021-10-03 14:41:54 +0000 <Solid> so DynamicLog docs would be great! :D
2021-10-03 14:55:26 +0000Ihaveaquestion(~Ihaveaque@78.175.178.18)
2021-10-03 14:58:07 +0000 <Ihaveaquestion> Hello
2021-10-03 14:58:10 +0000 <Ihaveaquestion> Some windows close when I make them too small. Can I make them not shrink more than a certain scale ?
2021-10-03 15:03:24 +0000 <Archanus[m]> <Ihaveaquestion> "Some windows close when I make..." <- Huh thats interesting, how many windows are you opening per screen?
2021-10-03 15:11:38 +0000 <Ihaveaquestion> Sorry for my poor english, when I shrink it with the mouse
2021-10-03 15:22:59 +0000Ihaveaquestion(~Ihaveaque@78.175.178.18) (Ping timeout: 256 seconds)
2021-10-03 15:24:51 +0000Ihaveaquestion(~Ihaveaque@78.171.12.232)
2021-10-03 15:42:57 +0000Ihaveaquestion(~Ihaveaque@78.171.12.232) (Quit: Client closed)
2021-10-03 15:50:28 +0000 <liskin> Solid, mc47[m]: I should be back from vacation tomorrow
2021-10-03 15:50:42 +0000 <liskin> At least somewhat
2021-10-03 15:51:31 +0000electr0n(~electr0n@about/security/founder/electr0n) (Quit: WeeChat 3.3)
2021-10-03 16:22:18 +0000werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-10-03 17:07:57 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 17:19:07 +0000geekosaur(~geekosaur@xmonad/geekosaur) (Remote host closed the connection)
2021-10-03 17:19:32 +0000geekosaur(~geekosaur@xmonad/geekosaur)
2021-10-03 17:36:17 +0000YusefAslam[m]1(~lol111mat@2001:470:69fc:105::1:ad7)
2021-10-03 18:01:07 +0000nomadxxxx3(~lanomadx@69.167.36.238)
2021-10-03 18:01:11 +0000 <YusefAslam[m]1> How do I escape the template text into multiple lines using the default XMobar config syntax, it is one huge line and is very hard to decipher currently?
2021-10-03 18:01:15 +0000 <YusefAslam[m]1> s/?/./
2021-10-03 18:01:30 +0000 <YusefAslam[m]1> s/How do I escape the template text into multiple lines using the default XMobar config syntax, it is one huge line and is very hard to decipher currently?/How do I escape the template text into multiple lines using the default XMobar config syntax (not the Haskell syntax), it is one huge line and is very hard to decipher currently./
2021-10-03 18:02:13 +0000nomadxx3(~lanomadx@69.167.45.89) (Ping timeout: 252 seconds)
2021-10-03 18:03:02 +0000YusefAslam[m]1STEVEOSSAS[m]
2021-10-03 18:04:03 +0000 <Solid> I don't know if the parser supports this, but seeing that the config syntax is a subset of haskell you could try a backslash followed by a newline to split the string
2021-10-03 18:07:01 +0000STEVEOSSAS[m]uploaded an image: (33KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/vhBOGhVhNoDRyhmhoeKXhvgS/Screenshot%2… >
2021-10-03 18:07:13 +0000 <STEVEOSSAS[m]> Tried this, XMobar doesn't recompile after
2021-10-03 18:08:53 +0000STEVEOSSAS[m]TORRENTER[m]
2021-10-03 18:14:32 +0000 <Solid> I suppose your only options are to either hack this into the config file format or to use haskell to configure xmobar then :)
2021-10-03 18:14:55 +0000 <TORRENTER[m]> K np, thanks for the help anyway :))
2021-10-03 18:29:22 +0000jokleinn(~jokleinn@user/jokleinn)
2021-10-03 19:29:14 +0000 <TORRENTER[m]> Hey guys, I have an issue with 2 XMobars: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting, while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to 99%,
2021-10-03 19:29:14 +0000 <TORRENTER[m]> after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably).
2021-10-03 19:29:22 +0000 <TORRENTER[m]> s/XMobars/XMobar instances/
2021-10-03 19:29:49 +0000 <TORRENTER[m]> s/Hey guys, I have an issue with 2 XMobars: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting, while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to
2021-10-03 19:29:49 +0000 <TORRENTER[m]> 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./Hey guys, I have an issue with 2 XMobar instances: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting (but respawning on itself, while the
2021-10-03 19:29:49 +0000 <TORRENTER[m]> previous process isn't killed), while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./
2021-10-03 19:33:28 +0000TORRENTER[m]uploaded an image: (20KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/vBHDSSZxROSwIDYtqEBOVTum/Screenshot%2… >
2021-10-03 19:33:48 +0000 <TORRENTER[m]> TORRENTER[m]: Main bit of config
2021-10-03 19:35:32 +0000TORRENTER[m]uploaded an image: (91KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/eJqfVwahXjywFisRBRAPMwjm/Screenshot%2… >
2021-10-03 19:35:33 +0000 <TORRENTER[m]> TORRENTER[m]: The rest of main
2021-10-03 19:36:45 +0000 <TORRENTER[m]> TORRENTER[m]: xmproc is the top bar on the main screen, xmprocbtmscr1 is the bottom bar on the main screen
2021-10-03 19:37:20 +0000 <TORRENTER[m]> StdinReader is only running on the bottom bar BTW
2021-10-03 19:39:12 +0000 <TORRENTER[m]> I have to do `killall xmobar` in the terminal, this kills all instances of the top bar and the one instance of the bottom bar.
2021-10-03 19:39:30 +0000 <TORRENTER[m]> * the terminal to actually kill the bar instances, this
2021-10-03 19:39:37 +0000 <TORRENTER[m]> * the terminal to actually instances, this
2021-10-03 19:39:59 +0000 <TORRENTER[m]> s/I have to do `killall xmobar` in the terminal, this kills all instances of the top bar and the one instance of the bottom bar./I have to do `killall xmobar` in the terminal to actually kill all the instances of the top bar./
2021-10-03 19:40:49 +0000 <TORRENTER[m]> s/I have to do `killall xmobar` in the terminal, this kills all instances of the top bar and the one instance of the bottom bar./I have to do `killall xmobar` in the terminal to actually kill all the instances of the top bar. /
2021-10-03 19:41:44 +0000 <TORRENTER[m]> But hitting the recompile keybind for XMonad (alt-q) restarts the top bar & bottom bar as normal. When hitting this keybind again, the top bar doesn't kill and then restart itself, it just restarts an makes a new instance on top of itself; The bottom bar acts normally though..
2021-10-03 19:41:55 +0000 <TORRENTER[m]> s/an/and/
2021-10-03 19:44:49 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 19:45:16 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 19:46:19 +0000 <TORRENTER[m]> This screenshot is proof that the top bar doesn't restart properly:
2021-10-03 19:46:33 +0000TORRENTER[m]uploaded an image: (15KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/DSkAAMdFmifpcgpedVMbhwIq/Screenshot%2… >
2021-10-03 19:47:57 +0000 <TORRENTER[m]> I'm on the stable version of XMonad, 0.15 BTW
2021-10-03 19:48:01 +0000 <TORRENTER[m]> Not the git version
2021-10-03 19:48:37 +0000 <TORRENTER[m]> s/Hey guys, I have an issue with 2 XMobars: One is at the top of the screen, one is at the bottom. I have an issue where one bar (e.g: top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting, while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to
2021-10-03 19:48:37 +0000 <TORRENTER[m]> 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./Hey guys, I have an issue with 2 XMobar instances: One is at the top of the screen, one is at the bottom. I have an issue where one bar (top bar) doesn't kill itself on recompile, but the other bar (the bottom one) kills itself and then restarts, why is one bar not restarting (but respawning on itself, while the
2021-10-03 19:48:37 +0000 <TORRENTER[m]> previous process isn't killed), while the other one restarts as normal? Is it maybe because I configured ppOutput wrong?? What is going on? (Also mentioning that the CPU skyrockets on recompile to 99%, after recompile it sits at 19-30% usage, this is because of the duplicate bars spawning on top of each other probably)./
2021-10-03 19:49:05 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 19:49:28 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 19:54:31 +0000 <mc47[m]> Since StdinReader isn't running on the top bar, there's no way to kill it
2021-10-03 19:54:40 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 19:55:03 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 19:56:26 +0000 <mc47[m]> Either use spawnOnce for the top bar so you don't restart it, add some logic to kill bars in your startupHook, or use XMonad.Hooks.StatusBar from the git version of contrib for a clean solution
2021-10-03 19:57:53 +0000 <mc47[m]> For the last option, you might want to check https://xmonad.org/INSTALL.html and https://xmonad.github.io/xmonad-docs/xmonad-contrib-0.16.999/XMonad-Hooks-StatusBar.html
2021-10-03 19:58:27 +0000 <TORRENTER[m]> Thanks! So you're saying either update or use a janky fix?
2021-10-03 19:58:45 +0000 <TORRENTER[m]> I'll stick with the janky fix for now, might switch to the git version later I guess..
2021-10-03 20:02:07 +0000 <TORRENTER[m]> s/?/../
2021-10-03 20:02:27 +0000 <TORRENTER[m]> s/a/the/, s/janky fix?/startupHook/
2021-10-03 20:02:37 +0000 <TORRENTER[m]> s/janky/startupHook/
2021-10-03 20:03:17 +0000 <TORRENTER[m]> s/I'm on the stable version of XMonad, 0.15 BTW/I'm on the stable version of XMonad, 0.15, and on the stable version of XMonad-Contrib too../
2021-10-03 20:06:21 +0000 <TORRENTER[m]> Anyway I would go about doing the startupHook fix you mentioned (I am a beginner sry..)
2021-10-03 20:06:27 +0000 <TORRENTER[m]> s/Anyway I would go about doing the startupHook fix you mentioned (I am a beginner sry..)/Any way I would go about doing the startupHook fix you mentioned (I am a beginner sry..)/
2021-10-03 20:09:13 +0000 <mc47[m]> Not sure if calling killall xmobar at the start of the hook would work (because of race conditions), so you're stuck with playing around with persistent states for now, which sadly isn't beginner friendly
2021-10-03 20:09:36 +0000 <mc47[m]> (no access to a computer right now, sorry)
2021-10-03 20:10:30 +0000 <mc47[m]> One thing you could do is use StdinReader in xmobar and send nothing to it from xmonad
2021-10-03 20:10:33 +0000 <mc47[m]> Might work
2021-10-03 20:11:27 +0000 <TORRENTER[m]> mc47[m]: Tried this a few mins ago, same thing happens unfortunately lol
2021-10-03 20:12:13 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 20:13:06 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 20:13:45 +0000 <TORRENTER[m]> I'll just wait until tmrw I guess, in the meantime I'll just use spawnOnce and just manually kill the bar if anything happens, thanks though :))
2021-10-03 20:15:01 +0000 <TORRENTER[m]> * use spawnOnce in the startupHook and just
2021-10-03 20:19:17 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 20:21:06 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 20:22:34 +0000 <TORRENTER[m]> s/I'll just wait until tmrw I guess, in the meantime I'll just use spawnOnce and just manually kill the bar if anything happens, thanks though :))/I'll just do this tmrw I guess, in the meantime I'll just use spawnOnce in the startupHook and just manually kill the bar if anything happens, thanks though :))/
2021-10-03 20:22:47 +0000 <TORRENTER[m]> s/I'll just wait until tmrw I guess, in the meantime I'll just use spawnOnce and just manually kill the bar if anything happens, thanks though :))/I'll just do this tmrw (or another day) I guess, in the meantime I'll just use spawnOnce in the startupHook and just manually kill the bar if anything happens, thanks though :))/
2021-10-03 21:12:28 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:12:52 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:13:07 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:14:08 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:23:46 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:24:15 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:24:31 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:25:11 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:27:01 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:27:19 +0000 <TORRENTER[m]> Anyone know if the git version of XMonad is usable currently? Does it crash alot??
2021-10-03 21:27:24 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:28:12 +0000 <geekosaur> it should be pretty stable; a number of people are running it currently, because we haven't had a release in so long and it has some major improvements
2021-10-03 21:28:23 +0000 <byorgey> TORRENTER[m]: the git version of XMonad is always rock-solid in my experience
2021-10-03 21:28:55 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:29:17 +0000 <geekosaur> last time we had a significant issue with crashing was because the Arch packager for the git version decided to ignore the bounds on X11
2021-10-03 21:29:23 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:29:56 +0000 <byorgey> I have been running xmonad for many years (10+?), I pretty much just randomly do a 'git pull' occasionally and rebuild whenever I feel like it. It has never crashed.
2021-10-03 21:34:19 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:34:43 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:35:07 +0000 <geekosaur> in general, when we have bugs they don't show up as crashes. (in xmonad or -contrib at least. every so often a bug is uncovered in the X11 bindings which affects xmonad, like aforementioned Arch issue)
2021-10-03 21:35:53 +0000 <TORRENTER[m]> Very nice! I think I will switch to the git version tmrw, I'm excited!!
2021-10-03 21:36:07 +0000 <geekosaur> most commonly they're backward compatibility issues which require xmonad.hs to be updated before it will compile againb
2021-10-03 21:37:11 +0000 <TORRENTER[m]> * version tmrw (or some other day soon), I'm
2021-10-03 21:44:51 +0000cjb(~cjb@user/cjb)
2021-10-03 21:46:38 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:47:01 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:47:55 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com) (Remote host closed the connection)
2021-10-03 21:48:30 +0000rekahsoft(~rekahsoft@cpe0008a20f982f-cm64777d666260.cpe.net.cable.rogers.com)
2021-10-03 21:59:41 +0000 <TORRENTER[m]> <geekosaur> "most commonly they're backward..." <- Does this mean I have to update my config before installing the git version? If so I dont mind anyway...
2021-10-03 22:01:38 +0000 <geekosaur> you might. check the changelog, it will say any backward compat issues: https://github.com/xmonad/xmonad-contrib/blob/master/CHANGES.md https://github.com/xmonad/xmonad/blob/master/CHANGES.md
2021-10-03 22:02:05 +0000 <geekosaur> actually we should list the XDG changes in the latter as potentially breaking, I think
2021-10-03 22:03:30 +0000 <geekosaur> since some corner cases behave differently now
2021-10-03 22:04:43 +0000 <geekosaur> we mostly try to avoid breaking older configs because people still pass around configs from the 0.9 days and expect them to work :)
2021-10-03 22:05:20 +0000 <geekosaur> and folks like byorgey who mostly have used the same xmonad.hs for many versions
2021-10-03 22:06:22 +0000 <geekosaur> (heck, I tweak things every few weeks but my basic xmonad.hs is unchanged since 2008 or thenabouts)
2021-10-03 22:13:34 +0000 <cjb> reading those changes, why is the binary going into XDG_CACHE_DIR? the temporary files make sense because if they are deleted it doesn't matter
2021-10-03 22:14:11 +0000 <geekosaur> the binary is also regenerated if it's not there
2021-10-03 22:14:45 +0000 <geekosaur> the only file that is really required is xmonad.hs (and any lib files it might use)
2021-10-03 22:15:12 +0000 <cjb> fair enough, just means login will take longer for people how have XDG_CACHE_DIR pointed to a tmpfs
2021-10-03 22:15:20 +0000 <cjb> s/how/who/
2021-10-03 22:15:45 +0000 <geekosaur> in my experience, even with a fairly complex xmonad.hs it takes about 2 seconds to compile
2021-10-03 22:16:01 +0000 <TORRENTER[m]> <geekosaur> "(heck, I tweak things every..." <- Very nice, this backwards compatibility that XMonad has is really handy, especially for lazy people like me lol
2021-10-03 22:16:30 +0000 <geekosaur> and that's on a slow, low memory laptop
2021-10-03 22:18:02 +0000 <cjb> my config takes 14s to recompile, but my computer is from the dark ages so probably doesn't matter too much. also I can work around this change by setting XMONAD_CACHE_DIR
2021-10-03 22:25:07 +0000electr0n(~electr0n@about/security/founder/electr0n)
2021-10-03 22:26:24 +0000 <Archanus[m]> <Ihaveaquestion> "Sorry for my poor english..." <- How small are you shrinking the windows? I just got on my pc and I'm able to shrink wi flows down to a 1x1 pixel square without any problems
2021-10-03 22:27:31 +0000 <geekosaur> it may be a specific application that crashes if the windows get too small
2021-10-03 22:28:19 +0000 <geekosaur> that said, such applications should really set the minimum and maximum window sizes if applicable instead of crashing
2021-10-03 22:28:50 +0000 <geekosaur> I think we obey those, at least
2021-10-03 22:30:43 +0000 <geekosaur> I know we look at them because if min, max, and default window size are all set the same, we autofloat at that size
2021-10-03 22:31:22 +0000 <Archanus[m]> geekosaur: O
2021-10-03 22:33:04 +0000 <Archanus[m]> geekosaur: I'm not entirely sure what theyre talking about, I', assuming manual resizing the window, but I'm unable to replicate the problem
2021-10-03 22:33:46 +0000 <geekosaur> yeh, that's how I read it as well
2021-10-03 22:39:12 +0000 <geekosaur> the question may be whether we properly obey WM_NORNMAL_HINTS
2021-10-03 22:39:48 +0000 <geekosaur> although I note ICCCM says the client has to accept the size the wm gives it, the size hints are only hints
2021-10-03 22:39:56 +0000 <geekosaur> so this may be a buggy client
2021-10-03 22:40:09 +0000 <geekosaur> (tiling window managers often provoke such bugs)
2021-10-03 22:41:35 +0000 <geekosaur> in any case, forcing a minimum in resize requires copying and reimplementing the resize code
2021-10-03 22:42:01 +0000 <geekosaur> there's no easy way to hook into it because it's spread over multiple events
2021-10-03 22:42:44 +0000 <geekosaur> in any case, they seem to have left
2021-10-03 22:43:15 +0000 <Archanus[m]> oh, I missed that, guess I didn't answer them fast enough
2021-10-03 22:44:07 +0000 <Archanus[m]> so, since I got you here, looking back on the previous conversation a bit, what would be the correct way of having xmonad.hs restart xmobar automatically?
2021-10-03 22:46:37 +0000seschwar(~seschwar@user/seschwar) (Quit: :wq)
2021-10-03 22:59:43 +0000 <geekosaur> probably to use the new StatusBar stuff since it does what people tend to expect
2021-10-03 23:00:01 +0000 <geekosaur> (it's in git xmonad/xmonad-contrib)
2021-10-03 23:00:25 +0000 <geekosaur> the old way assumed you were feeding it over a pipe so the old one would go away automatically on mod-q when xmonad did
2021-10-03 23:02:28 +0000 <geekosaur> StatusBar requires you to use its mechanisms for starting bars so it knows what to kill on restart
2021-10-03 23:04:58 +0000 <Archanus[m]> i' reading through the link now...not making all that much sense yet as I think I'm still running an older version of xmonad
2021-10-03 23:05:14 +0000 <Archanus[m]> yah, all my xmobars are running through pipes from xmonad
2021-10-03 23:06:43 +0000 <geekosaur> do they all use StdinReader?
2021-10-03 23:07:05 +0000 <geekosaur> because without that they won't be reading to notice the EOF when xmonad goes away
2021-10-03 23:07:08 +0000 <Archanus[m]> i'm not ready to upgrade quite yet I don't think, I ONLY just got my system set up to about 90% of what I want, it's basically useable now except for a few little things I haven't been able to figure out yet
2021-10-03 23:07:17 +0000 <Archanus[m]> geekosaur: yes
2021-10-03 23:08:06 +0000 <Archanus[m]> I think so
2021-10-03 23:08:39 +0000 <Archanus[m]> I'm actually a super noob still, I've learned a lot, but still have a long way to go so please bear with me
2021-10-03 23:11:19 +0000 <geekosaur> I'm not much of an expert on xmobar, but I do know you need StdinReader both in the Run stuff and in the template or xmobar will ignore it
2021-10-03 23:13:31 +0000 <Archanus[m]> huh, I didn't know that, let me see if that works or if I jsut broke my system again
2021-10-03 23:15:37 +0000SpiderPig(~matt@047-132-233-190.res.spectrum.com)
2021-10-03 23:17:18 +0000 <Archanus[m]> yeah, stdinreader just makes so the bar won't spawn
2021-10-03 23:18:12 +0000 <geekosaur> hm. can you check the log? (this is usually .xsession-errors but may be in journald / journalctl)
2021-10-03 23:19:16 +0000 <geekosaur> if you run startx from the console then you'll need to switch back to the text console to see the errors
2021-10-03 23:25:13 +0000 <Archanus[m]> hmm nothing is popping out at me from journalctl...I'll probably have to fiddle with things a bit to see what changed. it will probably have to be after work though... I can't get into it too deep right now
2021-10-03 23:26:08 +0000 <geekosaur> you could also try running it from a terminal to see what error messages it spits out
2021-10-03 23:26:11 +0000 <Archanus[m]> but this seems like the right place to get some support unless I am mistaken?
2021-10-03 23:26:23 +0000 <geekosaur> yes
2021-10-03 23:26:37 +0000 <geekosaur> just not really from me :(
2021-10-03 23:26:50 +0000 <geekosaur> maybe someone else will show up who can help more
2021-10-03 23:26:56 +0000 <Archanus[m]> I have like 3 issues and 2 things which would be nice to figure out how to do
2021-10-03 23:27:31 +0000 <Archanus[m]> no worries, you've already helped me a lot, thank you
2021-10-03 23:27:52 +0000 <Archanus[m]> at least in getting me pointed in the right direction of where to look
2021-10-03 23:31:08 +0000cyr4x3(~cyr4x3@139.47.115.87)
2021-10-03 23:34:01 +0000cyr4x3(~cyr4x3@139.47.115.87) (Client Quit)