Newest at the top
| 2025-05-14 11:19:09 +0200 | ChubaDuba | (~ChubaDuba@5.167.118.85) ChubaDuba |
| 2025-05-14 10:24:46 +0200 | ft | (~ft@p3e9bc106.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-05-14 08:41:58 +0200 | mc47 | (~yecinem@p200300ee0f0937c4015d0c59dcb97f85.dip0.t-ipconnect.de) |
| 2025-05-14 07:33:55 +0200 | haskellbridge | (~hackager@syn-096-028-227-029.res.spectrum.com) (Ping timeout: 276 seconds) |
| 2025-05-14 04:19:06 +0200 | td_ | (~td@i5387091D.versanet.de) |
| 2025-05-14 04:17:25 +0200 | td_ | (~td@i53870919.versanet.de) (Ping timeout: 265 seconds) |
| 2025-05-14 02:39:19 +0200 | sajenim | (~sajenim@user/sajenim) sajenim |
| 2025-05-14 01:40:03 +0200 | <L29Ah> | while my most pressing real problem is tkabber creating 70 chat windows being slow |
| 2025-05-14 01:39:36 +0200 | <L29Ah> | maybe because my benchmark was dealing with terminal windows though :/ |
| 2025-05-14 01:38:35 +0200 | <L29Ah> | played a bit with the config, and layoutHintsToCenter seems to have the biggest impact on window creation cpu consumption |
| 2025-05-14 01:18:59 +0200 | OftenFaded50 | (~OftenFade@user/tisktisk) (Quit: Client closed) |
| 2025-05-14 01:16:36 +0200 | <L29Ah> | ah right i can make xinitrc no longer a symlink to xsession |
| 2025-05-14 01:15:52 +0200 | <burp> | I have "exec xmonad" as the last line in my .xinitrc |
| 2025-05-14 01:13:57 +0200 | L29Ah | 's xsession is a mess |
| 2025-05-14 01:13:39 +0200 | <L29Ah> | now i need to recall a good way to start X with just the basic things like xmonad and pause() |
| 2025-05-14 01:11:18 +0200 | <burp> | well, definitely not normal, so bug/software combination, configuration, issue. I guess you could rule out configuration with a minimal example |
| 2025-05-14 01:08:24 +0200 | <L29Ah> | when windows spawn it gets top1 CPU consumption, next up goes X so might be that it does a lot of calls needlessly |
| 2025-05-14 01:07:47 +0200 | <L29Ah> | it's just slow |
| 2025-05-14 01:05:48 +0200 | <burp> | does it use a lot of CPU time? |
| 2025-05-14 01:05:37 +0200 | <burp> | what aspect of it is slow? |
| 2025-05-13 23:55:13 +0200 | catman | (~catman@user/catman) (Ping timeout: 252 seconds) |
| 2025-05-13 22:05:32 +0200 | haskellbridge | (~hackager@syn-096-028-227-029.res.spectrum.com) hackager |
| 2025-05-13 21:55:17 +0200 | yaslam | (~yaslam@user/yaslam) yaslam |
| 2025-05-13 21:54:01 +0200 | yaslam | (~yaslam@user/yaslam) (Remote host closed the connection) |
| 2025-05-13 21:43:56 +0200 | yaslam | (~yaslam@user/yaslam) yaslam |
| 2025-05-13 21:43:44 +0200 | yaslam_ | (~yaslam@user/yaslam) (Ping timeout: 245 seconds) |
| 2025-05-13 21:17:11 +0200 | <yaslam_> | I usually only have 4-10 windows open |
| 2025-05-13 21:12:57 +0200 | <yaslam_> | -90 |
| 2025-05-13 21:12:52 +0200 | <yaslam_> | -50 |
| 2025-05-13 21:12:41 +0200 | <L29Ah> | how many hundreds of windows do you have? |
| 2025-05-13 21:12:06 +0200 | <yaslam_> | L29Ah: it has never been slow for me |
| 2025-05-13 20:43:45 +0200 | mc47 | (~yecinem@host-82-135-127-100.customer.m-online.net) (Ping timeout: 260 seconds) |
| 2025-05-13 20:38:56 +0200 | OftenFaded50 | (~OftenFade@user/tisktisk) OftenFaded |
| 2025-05-13 20:24:31 +0200 | ft | (~ft@p3e9bc106.dip0.t-ipconnect.de) ft |
| 2025-05-13 20:23:21 +0200 | mc47 | (~yecinem@host-82-135-127-100.customer.m-online.net) |
| 2025-05-13 19:50:53 +0200 | mc47 | (~yecinem@host-82-135-127-100.customer.m-online.net) (Ping timeout: 265 seconds) |
| 2025-05-13 18:50:55 +0200 | mc47 | (~yecinem@host-82-135-127-100.customer.m-online.net) |
| 2025-05-13 18:44:42 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-05-13 18:29:02 +0200 | sajenim | (~sajenim@user/sajenim) (Ping timeout: 244 seconds) |
| 2025-05-13 18:07:06 +0200 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Read error: Connection reset by peer) |
| 2025-05-13 17:51:49 +0200 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) (Ping timeout: 248 seconds) |
| 2025-05-13 15:49:52 +0200 | <L29Ah> | xmonad is slow and i can't bring myself into profiling it because profiling haskell turned painful last times i did it :< |
| 2025-05-13 15:45:07 +0200 | Digit | (~user@user/digit) Digit |
| 2025-05-13 15:42:47 +0200 | Digit | (~user@user/digit) (Remote host closed the connection) |
| 2025-05-13 11:41:39 +0200 | dpn | (~dpn@203.220.95.204) dpn` |
| 2025-05-13 11:10:10 +0200 | werneta | (~werneta@syn-071-083-160-242.res.spectrum.com) werneta |
| 2025-05-13 11:06:33 +0200 | werneta | (~werneta@syn-071-083-160-242.res.spectrum.com) (Read error: Connection reset by peer) |
| 2025-05-13 10:29:22 +0200 | ft | (~ft@p3e9bc106.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-05-13 09:38:02 +0200 | mc47 | (~yecinem@host-212-114-138-22.customer.m-online.net) |
| 2025-05-13 08:14:31 +0200 | Leary | (~Leary@user/Leary/x-0910699) Leary |