2021/05/09

2021-05-09 00:17:26 +0000mc47(~yecinem@89.246.239.190)
2021-05-09 00:18:25 +0000ericsagn1(~ericsagne@2405:6580:0:5100:1174:bcc9:701e:5393)
2021-05-09 00:21:01 +0000ericsagnes(~ericsagne@i220-108-228-29.s42.a013.ap.plala.or.jp) (Ping timeout: 260 seconds)
2021-05-09 00:47:17 +0000mc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-05-09 01:13:43 +0000mohab(~mohab@156.223.213.174) (Ping timeout: 252 seconds)
2021-05-09 01:16:56 +0000ADG1089(~aditya@223.226.229.98)
2021-05-09 01:17:56 +0000ADG1089(~aditya@223.226.229.98) (Read error: Connection reset by peer)
2021-05-09 01:18:54 +0000yiufung(~user@183178189045.ctinets.com)
2021-05-09 01:30:09 +0000mohab(~mohab@156.223.213.174)
2021-05-09 01:38:52 +0000mohab(~mohab@156.223.213.174) (Ping timeout: 240 seconds)
2021-05-09 01:50:38 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-09 02:02:36 +0000heatwave(~heatwave@192.145.118.163)
2021-05-09 02:03:56 +0000heatwave_(~heatwave@ip-66-115-176-138.creativelink.net)
2021-05-09 02:07:06 +0000heatwave(~heatwave@192.145.118.163) (Ping timeout: 240 seconds)
2021-05-09 02:08:27 +0000 <heatwave_> Hi here! I updated to pipewire bluetooth drivers, and now xmobar's Volume widget cannot control the bluetooth volume. Is that not suported yet or will I need to implement a way to find the right source?
2021-05-09 02:10:56 +0000kajzer(~kajzer@unaffiliated/kajzer) (Quit: WeeChat 3.1)
2021-05-09 02:20:12 +0000theDon(~td@94.134.91.193) (Ping timeout: 240 seconds)
2021-05-09 02:22:19 +0000theDon(~td@muedsl-82-207-238-217.citykom.de)
2021-05-09 02:25:33 +0000yiufung(~user@183178189045.ctinets.com) (Ping timeout: 268 seconds)
2021-05-09 02:37:42 +0000geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com) (Ping timeout: 240 seconds)
2021-05-09 02:37:51 +0000heatwave(~heatwave@66.115.157.85)
2021-05-09 02:38:47 +0000heatwave(~heatwave@66.115.157.85) (Read error: Connection reset by peer)
2021-05-09 02:40:26 +0000heatwave(~heatwave@192.145.118.135)
2021-05-09 02:40:32 +0000heatwave_(~heatwave@ip-66-115-176-138.creativelink.net) (Ping timeout: 240 seconds)
2021-05-09 02:43:49 +0000heatwave_(~heatwave@192.145.118.233)
2021-05-09 02:45:42 +0000heatwave2(~heatwave@192.145.118.242)
2021-05-09 02:46:32 +0000heatwave(~heatwave@192.145.118.135) (Ping timeout: 240 seconds)
2021-05-09 02:48:22 +0000heatwave_(~heatwave@192.145.118.233) (Ping timeout: 268 seconds)
2021-05-09 03:28:57 +0000heatwave2(~heatwave@192.145.118.242) (Quit: WeeChat 3.1)
2021-05-09 04:02:52 +0000mohab(~mohab@156.223.213.174)
2021-05-09 05:29:36 +0000 <heck-to-the-gnom> Since when could it control the volume? I knew that it could read it, but write to it?
2021-05-09 05:29:52 +0000 <heck-to-the-gnom> That module, I find finnicky sometimes, alsa is a bit special :)
2021-05-09 05:30:28 +0000 <heck-to-the-gnom> I've had problems with it since day one, but it's not been all that bad, I've mostly used pavucontrol when xmobar's information on the subject fails me
2021-05-09 06:11:39 +0000ericsagn1(~ericsagne@2405:6580:0:5100:1174:bcc9:701e:5393) (Ping timeout: 245 seconds)
2021-05-09 06:24:15 +0000ericsagn1(~ericsagne@2405:6580:0:5100:9d04:a396:248a:e13a)
2021-05-09 06:56:13 +0000ADG1089(~aditya@223.226.229.98)
2021-05-09 07:08:16 +0000mohab(~mohab@156.223.213.174) (Ping timeout: 265 seconds)
2021-05-09 07:15:51 +0000mohab(~mohab@45.240.130.62)
2021-05-09 07:54:01 +0000idhugo(~idhugo@80-62-116-231-mobile.dk.customer.tdc.net)
2021-05-09 07:54:04 +0000idhugo(~idhugo@80-62-116-231-mobile.dk.customer.tdc.net) (Remote host closed the connection)
2021-05-09 07:57:59 +0000notis(~notis@85.203.44.173)
2021-05-09 08:09:35 +0000chemiker(~xarch@ip5f5a05e1.dynamic.kabel-deutschland.de)
2021-05-09 08:19:15 +0000ADG1089(~aditya@223.226.229.98) (Remote host closed the connection)
2021-05-09 08:36:43 +0000 <chemiker> Hi
2021-05-09 08:38:44 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-09 09:00:44 +0000seschwar(~seschwar@unaffiliated/seschwar)
2021-05-09 09:09:10 +0000eb0t(~eblip@unaffiliated/eblip)
2021-05-09 09:11:31 +0000def_jam(~eblip@unaffiliated/eblip) (Ping timeout: 265 seconds)
2021-05-09 09:23:30 +0000pmj(~pmj@ipbcc2919d.dynamic.kabel-deutschland.de)
2021-05-09 09:29:16 +0000eb0t(~eblip@unaffiliated/eblip) (Ping timeout: 252 seconds)
2021-05-09 09:34:27 +0000 <mc47[m]> Hi!
2021-05-09 09:37:26 +0000pmj(~pmj@ipbcc2919d.dynamic.kabel-deutschland.de) (Ping timeout: 240 seconds)
2021-05-09 09:38:10 +0000 <chemiker> Is it possible to have multiple "themes"/configs, so that i can hot switch them?
2021-05-09 09:39:43 +0000 <mc47[m]> No I don't think that's doable
2021-05-09 09:44:23 +0000eb0t(~eblip@unaffiliated/eblip)
2021-05-09 09:51:14 +0000eblip(~eblip@unaffiliated/eblip)
2021-05-09 09:51:37 +0000Nahra(~user@unaffiliated/nahra)
2021-05-09 09:53:38 +0000eb0t(~eblip@unaffiliated/eblip) (Ping timeout: 260 seconds)
2021-05-09 09:55:41 +0000 <Solid> I think that depends entirely on the extend of whta you mean by theme
2021-05-09 09:56:17 +0000 <Solid> I guess you could just toggle lots of things via an IORef or something
2021-05-09 09:56:25 +0000kajzer(~kajzer@unaffiliated/kajzer)
2021-05-09 09:57:45 +0000 <chemiker> I have done some research now and i think, that i can toggle them via key-binding and script.
2021-05-09 10:00:08 +0000 <chemiker> And it means, that themes are hot-switchable too.
2021-05-09 10:01:47 +0000 <Solid> xmonad doesn't really have any "themes" as such (besides perhaps prompt themes?), so I was confused by that
2021-05-09 10:01:58 +0000 <Solid> do you mean like GTK or QT themes?
2021-05-09 10:02:59 +0000 <chemiker> I mean like two separate configs.
2021-05-09 10:03:37 +0000 <chemiker> In ArcoLinux with bspwm you have some themes.
2021-05-09 10:17:52 +0000mohab(~mohab@45.240.130.62) (Ping timeout: 240 seconds)
2021-05-09 10:33:17 +0000mohab(~mohab@45.240.130.62)
2021-05-09 10:35:36 +0000 <mc47[m]> You probably can write an external script that recompiles the other config, symlinks it to where the binary is expected to be and restart xmonad
2021-05-09 10:36:04 +0000 <mc47[m]> But I feel like things might go wrong
2021-05-09 10:57:06 +0000mohab(~mohab@45.240.130.62) (Ping timeout: 260 seconds)
2021-05-09 11:02:16 +0000mc47(~yecinem@89.246.239.190)
2021-05-09 11:05:13 +0000materiyolo(~materiyol@112.205.57.255)
2021-05-09 12:00:39 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-09 12:33:47 +0000mohab(~mohab@45.240.130.62)
2021-05-09 12:54:21 +0000cfricke(~cfricke@unaffiliated/cfricke)
2021-05-09 12:57:11 +0000mohab(~mohab@45.240.130.62) (Ping timeout: 240 seconds)
2021-05-09 12:58:56 +0000mohab(~mohab@45.240.130.62)
2021-05-09 13:25:53 +0000geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com)
2021-05-09 13:25:55 +0000notis(~notis@85.203.44.173) (Read error: Connection reset by peer)
2021-05-09 13:38:17 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-09 13:46:45 +0000cfricke(~cfricke@unaffiliated/cfricke) (Ping timeout: 250 seconds)
2021-05-09 13:51:38 +0000pmj(~pmj@ipbcc2919d.dynamic.kabel-deutschland.de)
2021-05-09 14:10:56 +0000pmj(~pmj@ipbcc2919d.dynamic.kabel-deutschland.de) (Ping timeout: 260 seconds)
2021-05-09 14:12:07 +0000thoros(~thoros@193-154-186-236.adsl.highway.telekom.at)
2021-05-09 14:24:32 +0000mohab(~mohab@45.240.130.62) (Ping timeout: 240 seconds)
2021-05-09 14:29:14 +0000cfricke(~cfricke@unaffiliated/cfricke)
2021-05-09 14:39:59 +0000eric(~eric@pool-108-46-27-17.nycmny.fios.verizon.net)
2021-05-09 14:41:13 +0000 <eric> Sorry I'm a little bit of a noob but how do you autostart in xmonad? Should I just add what I want to Xsession
2021-05-09 14:47:46 +0000 <Solid> eric: there is a startupHook, but nothing hinders you from putting the stuff you want into Xsession, .xinitrc, or similar
2021-05-09 14:48:20 +0000 <eric> Solid: Thank you, should I just put the commands into the Startup Hook or make a autostart.sh
2021-05-09 14:50:14 +0000 <Solid> eric: it's entirely personal preference, really. The only thing one needs to look out for when using startupHook is that spawnOnce ( https://hackage.haskell.org/package/xmonad-contrib-0.16/docs/XMonad-Util-SpawnOnce.html#v:spawnOnce ) is probably what one wants to use instead of the normal spawn
2021-05-09 14:50:30 +0000 <Solid> (otherwise the respective programs will also spawn when restarting xmonad via M-q)
2021-05-09 14:50:43 +0000 <eric> Solid: Alright, thanks a lot have a nice day and stay safe!
2021-05-09 14:50:54 +0000 <Solid> You too! :)
2021-05-09 14:51:49 +0000notis(~notis@2a02:2149:8a44:5700:3fe0:286c:a70f:ba77)
2021-05-09 15:04:21 +0000s00pcan(~chris@075-133-056-178.res.spectrum.com) (Remote host closed the connection)
2021-05-09 15:19:04 +0000eric(~eric@pool-108-46-27-17.nycmny.fios.verizon.net) (Ping timeout: 252 seconds)
2021-05-09 15:26:50 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-09 15:28:15 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-09 15:34:15 +0000materiyolo(~materiyol@112.205.57.255) (Read error: Connection reset by peer)
2021-05-09 15:46:26 +0000s00pcan(~chris@075-133-056-178.res.spectrum.com)
2021-05-09 16:22:55 +0000mohab(~mohab@45.240.130.62)
2021-05-09 16:56:18 +0000 <mc47> I can't believe I only started using topics this week... I've been missing out
2021-05-09 17:04:12 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-09 17:11:02 +0000mc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-05-09 17:29:00 +0000 <Solid> It's great isn't it? :D
2021-05-09 17:43:24 +0000eric(~eric@pool-108-46-27-17.nycmny.fios.verizon.net)
2021-05-09 17:44:01 +0000erichissto
2021-05-09 17:56:14 +0000notis(~notis@2a02:2149:8a44:5700:3fe0:286c:a70f:ba77) (Ping timeout: 245 seconds)
2021-05-09 17:56:42 +0000 <Liskni_si> Is there a video of topic somewhere?
2021-05-09 18:06:54 +0000mc47(~yecinem@89.246.239.190)
2021-05-09 18:07:36 +0000 <mc47> Solid it's pretty great. I've expanded the TopicItem DSL to include topic groups from my last PR, and I'm liking it a lot
2021-05-09 18:08:39 +0000 <mc47> Liskni_si not sure
2021-05-09 18:14:55 +0000hissto(~eric@pool-108-46-27-17.nycmny.fios.verizon.net) (Quit: Konversation terminated!)
2021-05-09 18:23:35 +0000pmj(~pmj@ipbcc2919d.dynamic.kabel-deutschland.de)
2021-05-09 18:24:38 +0000rafadc(~rafadc@213.37.16.152.dyn.user.ono.com) (Read error: Connection reset by peer)
2021-05-09 18:27:54 +0000rafadc(~rafadc@213.37.16.152.dyn.user.ono.com)
2021-05-09 18:31:06 +0000incertia(~incertia@d4-50-26-103.nap.wideopenwest.com) (Ping timeout: 260 seconds)
2021-05-09 18:43:46 +0000chemiker(~xarch@ip5f5a05e1.dynamic.kabel-deutschland.de) ()
2021-05-09 18:57:11 +0000thoros(~thoros@193-154-186-236.adsl.highway.telekom.at) (Quit: WeeChat 3.0.1)
2021-05-09 19:26:39 +0000ericsagn1(~ericsagne@2405:6580:0:5100:9d04:a396:248a:e13a) (Ping timeout: 260 seconds)
2021-05-09 19:34:10 +0000 <Solid> mc47: oh that sounds pretty cool! I think I'll try to clean up the code and then submit a version of TopicItem upstream after all
2021-05-09 19:34:39 +0000 <Solid> if it fits you can hopefully extend it with that topic-groups support
2021-05-09 19:39:16 +0000ericsagn1(~ericsagne@2405:6580:0:5100:44a9:4dc5:2863:2677)
2021-05-09 19:42:56 +0000ircbrowse_tom(~ircbrowse@64.225.78.177)
2021-05-09 19:42:56 +0000Server+cnt
2021-05-09 20:17:00 +0000 <mc47> I think it's quite useful... erroneous states should not be representable, and that's not the case with the TopicSpace interface
2021-05-09 20:21:56 +0000pmj(~pmj@ipbcc2919d.dynamic.kabel-deutschland.de) (Ping timeout: 246 seconds)
2021-05-09 20:23:06 +0000Kamil[m](kamilmatri@gateway/shell/matrix.org/x-kndtlogddvvydmai)
2021-05-09 20:24:55 +0000mc47(~yecinem@89.246.239.190) (Quit: Leaving)
2021-05-09 20:33:06 +0000mohab(~mohab@45.240.130.62) (Ping timeout: 240 seconds)
2021-05-09 20:36:22 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-09 20:42:35 +0000notis(~notis@185.51.134.229)
2021-05-09 20:52:22 +0000tubep(~tpakkila@dsl-olubng11-54f80d-191.dhcp.inet.fi) (Ping timeout: 252 seconds)
2021-05-09 20:57:36 +0000tubep(~tpakkila@dsl-olubng11-54f80d-191.dhcp.inet.fi)
2021-05-09 21:43:46 +0000notis(~notis@185.51.134.229) (Ping timeout: 240 seconds)
2021-05-09 21:45:57 +0000notis(~notis@85.203.44.115)
2021-05-09 21:48:53 +0000mc47(~yecinem@89.246.239.190)
2021-05-09 21:53:18 +0000mohab(~mohab@45.240.130.62)
2021-05-09 22:04:47 +0000seschwar(~seschwar@unaffiliated/seschwar) (Quit: :wq)
2021-05-09 22:44:34 +0000mohab(~mohab@45.240.130.62) (Ping timeout: 252 seconds)
2021-05-09 22:45:27 +0000mohab(~mohab@45.240.130.62)
2021-05-09 22:55:13 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-09 22:55:43 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-09 22:58:19 +0000cfricke(~cfricke@unaffiliated/cfricke) (Ping timeout: 245 seconds)
2021-05-09 23:19:03 +0000kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-09 23:26:02 +0000notis(~notis@85.203.44.115) (Ping timeout: 246 seconds)
2021-05-09 23:51:15 +0000growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net)