2021/05/04

2021-05-04 00:04:56 +0200kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-04 00:11:29 +0200drl(~l@2600:1700:8360:3870:1aa:41f8:bbb8:d2b5)
2021-05-04 00:14:52 +0200mohab(~mohab@45.243.72.186)
2021-05-04 01:29:09 +0200kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-04 01:37:29 +0200notis(~notis@185.51.134.222) (Ping timeout: 246 seconds)
2021-05-04 01:40:13 +0200drl(~l@2600:1700:8360:3870:1aa:41f8:bbb8:d2b5) (Quit: Leaving)
2021-05-04 01:41:18 +0200sagax(~sagax_nb@213.138.71.146)
2021-05-04 01:54:38 +0200mohab(~mohab@45.243.72.186) (Ping timeout: 246 seconds)
2021-05-04 01:57:05 +0200drl(~l@2600:1700:8360:3870:911b:9f71:ef6d:14e8)
2021-05-04 02:27:03 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com) (Ping timeout: 240 seconds)
2021-05-04 02:27:28 +0200mc47(~yecinem@89.246.239.190) (Remote host closed the connection)
2021-05-04 02:37:14 +0200drl(~l@2600:1700:8360:3870:911b:9f71:ef6d:14e8) (Remote host closed the connection)
2021-05-04 03:06:37 +0200mohab(~mohab@45.243.72.186)
2021-05-04 03:29:09 +0200ADG1089(~aditya@223.236.186.113)
2021-05-04 04:04:19 +0200materiyolo(~materiyol@112.205.57.255)
2021-05-04 04:05:41 +0200s00pcan(~chris@107.181.165.217) (Ping timeout: 240 seconds)
2021-05-04 04:07:45 +0200s00pcan(~chris@075-133-056-178.res.spectrum.com)
2021-05-04 04:14:15 +0200ds5150(a689532e@166.137.83.46)
2021-05-04 04:15:08 +0200ds5150(a689532e@166.137.83.46) (Client Quit)
2021-05-04 04:25:29 +0200theDon(~td@94.134.91.148) (Ping timeout: 246 seconds)
2021-05-04 04:27:38 +0200theDon(~td@94.134.91.246)
2021-05-04 04:40:38 +0200kajzer(~kajzer@unaffiliated/kajzer) (Quit: WeeChat 3.1)
2021-05-04 05:19:58 +0200Bruners(lasseb@gateway/shell/tihlde/x-ycfybbsptydrkrbl) (Ping timeout: 240 seconds)
2021-05-04 05:23:12 +0200Bruners(lasseb@gateway/shell/tihlde/x-sqngxlewbsyanjez)
2021-05-04 05:27:20 +0200ADG1089(~aditya@223.236.186.113) (Remote host closed the connection)
2021-05-04 06:37:56 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Quit: leaving)
2021-05-04 06:38:23 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 06:39:17 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Client Quit)
2021-05-04 06:39:36 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 06:39:43 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Client Quit)
2021-05-04 06:39:59 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 06:41:53 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Client Quit)
2021-05-04 06:42:12 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 06:43:27 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Client Quit)
2021-05-04 06:43:44 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 06:44:13 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Client Quit)
2021-05-04 07:41:57 +0200ADG1089(~aditya@122.163.161.198)
2021-05-04 07:47:11 +0200mohab(~mohab@45.243.72.186) (Ping timeout: 252 seconds)
2021-05-04 07:48:03 +0200growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net) (Quit: ZNC 1.8.2 - https://znc.in)
2021-05-04 07:48:34 +0200ADG1089(~aditya@122.163.161.198) (Remote host closed the connection)
2021-05-04 07:53:13 +0200ADG1089(~aditya@122.163.161.198)
2021-05-04 08:06:40 +0200notis(~notis@185.51.134.222)
2021-05-04 08:08:21 +0200wonko7(~wonko7@62.115.229.50)
2021-05-04 08:11:05 +0200ADG1089(~aditya@122.163.161.198) (Quit: Konversation terminated!)
2021-05-04 08:12:38 +0200ADG1089(~aditya@122.163.161.198)
2021-05-04 08:14:02 +0200seschwar(~seschwar@unaffiliated/seschwar)
2021-05-04 08:14:11 +0200 <ADG1089> meta-q for restarting xmonad isn't working for me, how can i debug that? it's working when i use `xmonad --restart &`
2021-05-04 08:23:16 +0200srk(~sorki@unaffiliated/srk) (Quit: ZNC 1.8.1 - https://znc.in)
2021-05-04 08:24:50 +0200srk(~sorki@unaffiliated/srk)
2021-05-04 08:41:34 +0200mohab(~mohab@45.243.72.186)
2021-05-04 08:50:14 +0200cfricke(~cfricke@unaffiliated/cfricke)
2021-05-04 08:56:19 +0200ADG1089(~aditya@122.163.161.198) (Remote host closed the connection)
2021-05-04 09:03:54 +0200thc202(~thc202@unaffiliated/thc202)
2021-05-04 09:40:22 +0200cfricke(~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.1)
2021-05-04 09:44:14 +0200oogeek(~szz_@84.17.34.145)
2021-05-04 09:45:56 +0200 <oogeek> So does xmonad treats multiple monitors as a single display? I am reading the source code of X.H.ScreenCorner and it seems that it treats it like that.
2021-05-04 09:49:09 +0200cfricke(~cfricke@unaffiliated/cfricke)
2021-05-04 09:49:18 +0200 <oogeek> When multiple monitors are used, I want to restrict the four corners to be monitor aware. By setting the width and height of the SCLowerRight, SCUpperLeft,..., I can do that. However, is it worth to pass a list of tuple (0,0) (1920,0) (4480,0) to the "addScreenCorner function" and rewrite some functions?
2021-05-04 09:50:05 +0200 <oogeek> With 1920x1080 + 2560x1440 displays
2021-05-04 10:19:21 +0200kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de)
2021-05-04 10:23:46 +0200mohab(~mohab@45.243.72.186) (Ping timeout: 252 seconds)
2021-05-04 10:37:50 +0200mohab(~mohab@45.243.72.186)
2021-05-04 11:30:23 +0200materiyolo(~materiyol@112.205.57.255) (Quit: WeeChat 3.0.1)
2021-05-04 12:11:55 +0200mohab(~mohab@45.243.72.186) (Ping timeout: 252 seconds)
2021-05-04 12:24:28 +0200kajzer(~kajzer@unaffiliated/kajzer)
2021-05-04 12:25:38 +0200Natch(~Natch@c-e070e255.014-297-73746f25.bbcust.telenor.se) (Remote host closed the connection)
2021-05-04 12:31:02 +0200Natch(~Natch@c-e070e255.014-297-73746f25.bbcust.telenor.se)
2021-05-04 12:45:12 +0200mc47(~yecinem@89.246.239.190)
2021-05-04 13:33:15 +0200ericsagnes(~ericsagne@2405:6580:0:5100:4bd1:656f:4270:d212) (Ping timeout: 260 seconds)
2021-05-04 13:40:35 +0200mohab(~mohab@45.243.72.186)
2021-05-04 13:41:31 +0200notis(~notis@185.51.134.222) (Ping timeout: 260 seconds)
2021-05-04 13:46:46 +0200ericsagnes(~ericsagne@2405:6580:0:5100:a104:d14:93ae:b6b0)
2021-05-04 13:56:11 +0200IanLiu(~ian@187.11.111.13)
2021-05-04 13:57:18 +0200 <IanLiu> Have you ever experienced delays when opening Gnome applications? I've seen people with the same problem on the web, I've tried all kinds of solutions but none worked for me. Here is my xinitrc: http://ix.io/3lLb/sh . Any help?
2021-05-04 14:02:02 +0200 <IanLiu> ^ oops, sorry, wrong channel.
2021-05-04 14:09:07 +0200IanLiu(~ian@187.11.111.13) (Quit: WeeChat 3.1)
2021-05-04 14:41:54 +0200totte(~totte@chakra/totte)
2021-05-04 14:50:17 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com)
2021-05-04 14:59:05 +0200 <Solid> a morning wastes for an idea that was already implemented
2021-05-04 14:59:06 +0200 <Solid> sigh
2021-05-04 14:59:09 +0200 <Solid> s/tes/ted/
2021-05-04 15:02:05 +0200 <mc47> I hope you didn't waste too much time on it :/
2021-05-04 15:02:42 +0200 <mc47> The abstraction you added is cool and more versatile though, I wonder if that could be helpful somewhere else
2021-05-04 15:03:39 +0200 <mc47> I didn't make a good job making the loggers I added though, so sorry for that
2021-05-04 15:07:02 +0200 <oogeek> So does xmonad treats multiple monitors as a single display? I am reading the source code of X.H.ScreenCorner and it seems that it treats it like that.
2021-05-04 15:07:21 +0200 <oogeek> When multiple monitors are used, I want to restrict the four corners to be monitor aware. By setting the width and height of the SCLowerRight, SCUpperLeft,..., I can do that. However, is it worth to pass a list of tuple (0,0) (1920,0) (4480,0) to the "addScreenCorner function" and rewrite some functions?
2021-05-04 15:07:23 +0200notis(~notis@185.51.134.229)
2021-05-04 15:08:54 +0200 <Liskni_si> oogeek: xmonad doesn't, X.H.ScreenCorner does
2021-05-04 15:09:43 +0200 <oogeek> So is it worth to add a bit more parameter for X.H.ScreenCorner?
2021-05-04 15:09:56 +0200 <oogeek> For multiple monitors
2021-05-04 15:10:25 +0200 <Solid> mc47: ah it fine, I needed some break from writing my thesis anyways :)
2021-05-04 15:10:39 +0200 <Liskni_si> oogeek: Not really, the module is broken in multiple ways and could use a rewrite :-/
2021-05-04 15:11:30 +0200 <oogeek> Liskni_si Broken? Can you elaborate a bit more?
2021-05-04 15:11:32 +0200 <Liskni_si> It's basically entirely unaware of multiple screens and the possibility of screen layout changes
2021-05-04 15:11:43 +0200 <oogeek> Oh
2021-05-04 15:13:05 +0200 <mc47> Solid I feel you, kinda in the same spot
2021-05-04 15:13:33 +0200 <mc47> whereas for me it's coding rather than writing, that'll come later
2021-05-04 15:13:53 +0200 <oogeek> Solid mc47 So after seeing your discussion on PR #535, I was thinking how I can make a title function be screen aware, I mean, right now on two monitors, each bar show the same title. However, I want the screen with no focus to show nothing. Is that possible, I need some hint as to how to tweak it.
2021-05-04 15:15:15 +0200 <mc47> definitely, look at logWhenActive and logCurrentOnScreen
2021-05-04 15:16:13 +0200 <oogeek> mc47 Thanks, let me take a look.
2021-05-04 15:16:13 +0200 <mc47> https://github.com/TheMC47/dotfiles/blob/master/xmonad/.xmonad/xmonad.hs#L286
2021-05-04 15:16:22 +0200mohab(~mohab@45.243.72.186) (Ping timeout: 252 seconds)
2021-05-04 15:16:52 +0200 <mc47> If you don't want to show anything at all when the screen isn't active, just wrap the logger in logWhenActive
2021-05-04 15:17:08 +0200 <mc47> I use it here https://github.com/TheMC47/dotfiles/blob/master/xmonad/.xmonad/xmonad.hs#L301
2021-05-04 15:17:36 +0200mohab(~mohab@45.243.72.186)
2021-05-04 15:19:08 +0200 <Solid> mc47: no coding for my thesis, so xmonad is a nice change of pace for me =)
2021-05-04 15:19:29 +0200growpotkin(~growpotki@130-45-30-154.dyn.grandenetworks.net)
2021-05-04 15:19:59 +0200 <oogeek> One reason I start reading the source code of X.H.ScreenCorner is because I just had a algorithm exam this morning.
2021-05-04 15:20:04 +0200 <oogeek> Need something to relax
2021-05-04 15:20:32 +0200 <Solid> Liskni_si: r.e. what you said about unecessary calls to getName: should I just re-open #535, remove ppTitleUnfocused completely and add something like it to X.U.Loggers (a module I had never consciously acknowledged until today)?
2021-05-04 15:26:51 +0200 <oogeek> mc47 Thanks a lot. The log* works really well.
2021-05-04 15:26:58 +0200 <mc47> Awesome!
2021-05-04 15:27:08 +0200 <Liskni_si> Solid: possibly :-)
2021-05-04 15:29:44 +0200 <oogeek> I think that it would be a lot easier to put screen-aware logger functions to ppExtra, and then wrap PP with ScreenId -> PP
2021-05-04 15:33:50 +0200 <mc47> not sure I understand what you mean
2021-05-04 15:34:06 +0200 <mc47> ppExtras should stay blank, per default. It's up to the users to put what they want there
2021-05-04 15:34:54 +0200 <mc47> But having a function that makes a PP screen aware might be a good idea
2021-05-04 15:34:57 +0200 <oogeek> Yeah, I mean like the example in your config, if users want to use ppExtra together with log*, it would be easier.
2021-05-04 15:35:30 +0200 <oogeek> I don't mean that we should hardwire it to ppExtras, sorry for the misunderstanding.
2021-05-04 15:35:30 +0200 <mc47> It would have to be ScreenId -> X PP probably
2021-05-04 15:36:26 +0200 <mc47> that's a fun idea to play with :)
2021-05-04 15:37:17 +0200 <oogeek> mc47: Also, for my PR on sampleHook for X.A.CopyWindow, do you mean that I should add copiesPP directly to the source code?
2021-05-04 15:39:07 +0200 <mc47> Yes, but not as it is. It would take a function as a parameter to be applied when "ws `elem` copies" is true, and otherwise uses ppHidden from the given PP
2021-05-04 15:39:15 +0200 <mc47> I think it provides a better UX
2021-05-04 15:40:16 +0200 <oogeek> Got it, so I think basically users can pass "String -> String" to it. Is that right?
2021-05-04 15:41:23 +0200 <mc47> Rather WorkspaceId -> String, like ppHidden
2021-05-04 15:41:55 +0200 <mc47> Which is the same as String -> String, but consistent with the rest of the codebase :)
2021-05-04 15:42:09 +0200 <oogeek> Oh OK, let me edit it and push again. :)
2021-05-04 15:42:27 +0200 <oogeek> Yeah, right now in the codebase WorkspaceId :: String
2021-05-04 15:44:51 +0200ml|(~ml|@unaffiliated/ml/x-3958674) (Ping timeout: 246 seconds)
2021-05-04 15:58:51 +0200ml|(~ml|@unaffiliated/ml/x-3958674)
2021-05-04 16:06:53 +0200wonko7(~wonko7@62.115.229.50) (Ping timeout: 246 seconds)
2021-05-04 16:09:49 +0200wonko7(~wonko7@62.115.229.50)
2021-05-04 16:10:17 +0200 <oogeek> 2021-05-02 05:35:39 +0000 <oogeek> I have an idea about a new "good first issue".
2021-05-04 16:10:20 +0200 <oogeek> 2021-05-02 05:37:06 +0000 <oogeek> That is, in X.L.ResizableTile, define a new message that will set the horizontal ratio of windows to default. For example, I have 2 windows, now horizontally, one takes 1/3, another takes 2/3, by a message, I will reset them to 1/2
2021-05-04 16:10:25 +0200 <oogeek> 2021-05-02 05:38:17 +0000 <oogeek> However, the 1/2 (or something else) can be get from the resizableTall constructor.
2021-05-04 16:10:27 +0200 <oogeek> 2021-05-02 05:38:54 +0000 <oogeek> I find it useful and I have already tried to add it. It works OK.
2021-05-04 16:10:31 +0200 <oogeek> 2021-05-02 05:39:22 +0000 <oogeek> I think the use-case is that sometimes after ratio changing, you want to reset to default.
2021-05-04 16:10:35 +0200 <oogeek> Oh sorry
2021-05-04 16:10:52 +0200 <oogeek> The format is not good.
2021-05-04 16:12:52 +0200 <oogeek> So basically I have an idea of adding a new message to X.L.ResizableTile and the message will trigger action to reset the ratio of windows to, say, (1/2). Resizable 1 (1/300) (1/2) []
2021-05-04 16:13:15 +0200 <oogeek> Solid I am not sure if that can be a "good first issue"
2021-05-04 16:38:30 +0200cfricke(~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.1)
2021-05-04 16:38:39 +0200totte(~totte@chakra/totte) (Quit: ZNC - http://znc.in)
2021-05-04 16:44:44 +0200oogeek(~szz_@84.17.34.145) (Ping timeout: 268 seconds)
2021-05-04 17:00:45 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com) (Quit: Connection closed)
2021-05-04 17:06:12 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com)
2021-05-04 17:08:10 +0200ADG1089(~aditya@122.163.161.198)
2021-05-04 17:08:47 +0200totte(~totte@chakra/totte)
2021-05-04 17:30:11 +0200wonko7(~wonko7@62.115.229.50) (Ping timeout: 240 seconds)
2021-05-04 17:30:44 +0200antoniotrkdz(2d8b63d4@gateway/web/cgi-irc/kiwiirc.com/ip.45.139.99.212)
2021-05-04 17:31:07 +0200 <antoniotrkdz> hi
2021-05-04 17:31:35 +0200notis(~notis@185.51.134.229) (Ping timeout: 246 seconds)
2021-05-04 17:33:48 +0200notis(~notis@2a02:2149:8a44:5700:3fe0:286c:a70f:ba77)
2021-05-04 17:53:40 +0200ADG1089(~aditya@122.163.161.198) (Remote host closed the connection)
2021-05-04 17:53:56 +0200totte(~totte@chakra/totte) (Excess Flood)
2021-05-04 17:55:14 +0200totte(~totte@chakra/totte)
2021-05-04 18:07:26 +0200totte_(~totte@chakra/totte)
2021-05-04 18:08:01 +0200totteGuest48484
2021-05-04 18:08:01 +0200Guest48484(~totte@chakra/totte) (Killed (tepper.freenode.net (Nickname regained by services)))
2021-05-04 18:08:02 +0200totte_totte
2021-05-04 18:11:51 +0200wonko7(~wonko7@62.115.229.50)
2021-05-04 18:14:18 +0200ADG1089(~aditya@122.163.161.198)
2021-05-04 18:16:02 +0200 <Solid> mh I wonder, what's the general feel for X.U.Loggers (I've never used it)? If I create something like logTitles, should I give back an `X [String]` and let the user handle formatting however they like?
2021-05-04 18:16:13 +0200 <Solid> Should I take some `String -> String` formatting functions?
2021-05-04 18:16:32 +0200 <Solid> Should I use the WindowInfo abstraction somehow?
2021-05-04 18:16:38 +0200 <Solid> I feel like most of these would break composition
2021-05-04 18:16:52 +0200xsperry(~as@unaffiliated/xsperry)
2021-05-04 18:17:13 +0200 <Solid> But the `Logger = X (Maybe String)` abstraction just doesn't quite fit when you want to operate on multiple things
2021-05-04 18:20:15 +0200thc202(~thc202@unaffiliated/thc202) (Quit: thc202)
2021-05-04 18:21:06 +0200wonko7(~wonko7@62.115.229.50) (Ping timeout: 240 seconds)
2021-05-04 18:24:57 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 18:27:58 +0200thc202(~thc202@unaffiliated/thc202)
2021-05-04 18:32:41 +0200 <Solid> ?tell oogeek feel free to implement it yourself
2021-05-04 18:33:44 +0200 <Solid> lambdabot dead? :o
2021-05-04 18:34:12 +0200 <lambdabot> Consider it noted.
2021-05-04 18:34:22 +0200 <geekosaur> it was pretty slow for me a few minutes ago --- there it is
2021-05-04 18:34:26 +0200 <Solid> ah
2021-05-04 18:49:39 +0200wonko7(~wonko7@62.115.229.50)
2021-05-04 18:57:52 +0200wonko7(~wonko7@62.115.229.50) (Ping timeout: 240 seconds)
2021-05-04 19:22:34 +0200notis(~notis@2a02:2149:8a44:5700:3fe0:286c:a70f:ba77) (Ping timeout: 276 seconds)
2021-05-04 19:24:10 +0200notis(~notis@185.51.134.229)
2021-05-04 19:24:34 +0200thunderrd(~thunderrd@183.182.110.252) (Ping timeout: 268 seconds)
2021-05-04 19:26:15 +0200ADG1089__(~aditya@171.76.152.88)
2021-05-04 19:28:10 +0200ADG1089(~aditya@122.163.161.198) (Ping timeout: 265 seconds)
2021-05-04 19:28:48 +0200mohab(~mohab@45.243.72.186) (Remote host closed the connection)
2021-05-04 19:29:43 +0200ericsagnes(~ericsagne@2405:6580:0:5100:a104:d14:93ae:b6b0) (Ping timeout: 276 seconds)
2021-05-04 19:32:29 +0200ml|(~ml|@unaffiliated/ml/x-3958674) (Ping timeout: 268 seconds)
2021-05-04 19:33:33 +0200cfricke(~cfricke@unaffiliated/cfricke)
2021-05-04 19:38:30 +0200thunderrd(~thunderrd@183.182.114.223)
2021-05-04 19:41:52 +0200ericsagnes(~ericsagne@2405:6580:0:5100:1f8e:c408:8077:5927)
2021-05-04 19:57:05 +0200mohab(~mohab@45.243.72.186)
2021-05-04 19:59:18 +0200ryjm(sid383513@gateway/web/irccloud.com/x-mfvpahefkuhsmhxj) (Ping timeout: 258 seconds)
2021-05-04 20:01:57 +0200ryjm(sid383513@gateway/web/irccloud.com/x-hegmsdgmbwucdfbi)
2021-05-04 20:02:44 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net) (Remote host closed the connection)
2021-05-04 20:09:08 +0200wonko7(~wonko7@62.115.229.50)
2021-05-04 20:09:11 +0200mohab(~mohab@45.243.72.186) (Read error: Connection reset by peer)
2021-05-04 20:12:07 +0200mohab(~mohab@45.243.72.186)
2021-05-04 20:15:39 +0200notis(~notis@185.51.134.229) (Read error: Connection reset by peer)
2021-05-04 20:16:35 +0200werneta(~werneta@70-142-214-115.lightspeed.irvnca.sbcglobal.net)
2021-05-04 20:22:39 +0200ADG1089__(~aditya@171.76.152.88) (Remote host closed the connection)
2021-05-04 20:29:31 +0200ml|(~ml|@unaffiliated/ml/x-3958674)
2021-05-04 20:32:24 +0200mohab(~mohab@45.243.72.186) (Ping timeout: 252 seconds)
2021-05-04 20:36:19 +0200cfricke(~cfricke@unaffiliated/cfricke) (Quit: WeeChat 3.1)
2021-05-04 22:04:14 +0200kelnoky(~shao@ip1f128ba7.dynamic.kabel-deutschland.de) (Quit: WeeChat 3.1)
2021-05-04 22:10:14 +0200thc202(~thc202@unaffiliated/thc202) (Quit: thc202)
2021-05-04 22:10:18 +0200notis(~notis@185.51.134.229)
2021-05-04 22:18:14 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com) (Quit: Connection closed)
2021-05-04 22:21:05 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com)
2021-05-04 22:33:55 +0200 <mc47> Solid tbh I don't think it's used that much, it practically offers no new interesting functionality
2021-05-04 22:35:09 +0200 <mc47> At least in 0.16, all functionality is either covered by PP or by the status bars themselves, so there was little incentive to use X.U.Loggers
2021-05-04 22:37:37 +0200 <geekosaur> and most interesting functionality can't reasonably be done there because xmonad only wakes up on X11 events, not e.g. time or various system status changes
2021-05-04 22:37:58 +0200 <mc47> yes, the battery logger is totally useless for example
2021-05-04 22:38:22 +0200mohab(~mohab@45.243.72.186)
2021-05-04 22:38:56 +0200 <mc47> and there's making the information bound to a particular screen - logTitles would need to get reimplemented for that too :/
2021-05-04 22:40:25 +0200 <mc47> I feel this is going to explode... I'm tempted to remove some of the loggers I added (the layout and title ones at least) and experiment with some "ScreenId -> PP -> X PP" modifier
2021-05-04 22:41:56 +0200 <mc47> basically use state to freeze the PP when the screen is inactive
2021-05-04 22:42:59 +0200 <mc47> oh. that won't work. we need to change dynamicLogString
2021-05-04 22:43:09 +0200mc47sighs
2021-05-04 22:49:54 +0200 <mc47> We could add a ppScren :: Maybe (ScreenId) and set the default to Nothing, and then basically decide whether we run dynamicLogString, or just return the last generated string... It will be tricky though to get it working with more than one PP per screen, and there's also the problem of what we show at startup
2021-05-04 23:42:32 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com) (Quit: Connection closed)
2021-05-04 23:42:55 +0200geekosaur(930099da@rrcs-147-0-153-218.central.biz.rr.com)