Newest at the top
| 2026-02-27 20:34:38 +0100 | Enrico63 | (~Enrico63@host-80-104-109-187.retail.telecomitalia.it) Enrico63 |
| 2026-02-27 18:08:56 +0100 | <haskellbridge> | <Enrico Maria De Angelis> Thanks for the explanation |
| 2026-02-27 17:59:21 +0100 | <geekosaur> | which is why the shell, which is what usually sets it originally, is the only thing that can restore it properly |
| 2026-02-27 17:57:33 +0100 | <geekosaur> | the best they can do is clear or set it to something neutral |
| 2026-02-27 17:57:17 +0100 | <geekosaur> | technically not bugs, because there's one kinda big complication: apps can't read the titlebar, so they can't restore it |
| 2026-02-27 17:25:36 +0100 | <Leary> | I haven't had that issue for years now; some zsh configuration just handles it. |
| 2026-02-27 17:24:33 +0100 | <haskellbridge> | <Enrico Maria De Angelis> Are those all techinically bugs of those applications? 😅 |
| 2026-02-27 17:17:00 +0100 | <geekosaur> | I have a bunch of shell aliases/wrappers just to do cleanups |
| 2026-02-27 17:16:39 +0100 | <geekosaur> | yeh, and that's moderately common (vim doesn't clean up its titlebar changes either) |
| 2026-02-27 16:38:12 +0100 | <haskellbridge> | <Enrico Maria De Angelis> Yeah, that's the case, thanks @Leary :D |
| 2026-02-27 16:36:37 +0100 | <haskellbridge> | <Enrico Maria De Angelis> Oh, right, ahah. Let me see if that's the case |
| 2026-02-27 16:35:07 +0100 | <Leary> | Enrico: It may just be urvxt not resetting the window title---you could check this with xprop. |
| 2026-02-27 16:33:13 +0100 | <haskellbridge> | <Enrico Maria De Angelis> https://kf8nh.com/_heisenbridge/media/matrix.org/FMFYWUaPqDejbiVdpRCcUaMP/lcRaSdG8GJ0/xmonadlog.gif |
| 2026-02-27 16:33:05 +0100 | <haskellbridge> | <Enrico Maria De Angelis> Oh, I forgot to attach the GIF I recorded. Here it is: |
| 2026-02-27 16:32:31 +0100 | <haskellbridge> | <Enrico Maria De Angelis> I'm asking here because I start from the assumption that Xmobar is just writing whatever XMonad sends to it. After all, those "[" and "]" around the name of the windows, and the colors with which this stuff is shown is configured in XMonad configuration file, so if Xmobar is showing that, it is most likely just receiving a string from XMonad, no? |
| 2026-02-27 16:29:51 +0100 | <haskellbridge> | ... long message truncated: https://kf8nh.com/_heisenbridge/media/kf8nh.com/HYSbZusciHOxFKSDAjnfeaJq/qVsoZsXT1sQ (9 lines) |
| 2026-02-27 16:29:48 +0100 | <haskellbridge> | <Enrico Maria De Angelis> Hi there. I use XMonad with Xmobar, and use the XMonadLog plugin to show available workspaces, layout and so on. Today I've noticed something that feels like a but. It could well be a bug in my config, eh, but I don't know where it could be. |
| 2026-02-27 16:13:20 +0100 | Enrico63 | (~Enrico63@host-80-104-109-187.retail.telecomitalia.it) (Quit: Client closed) |
| 2026-02-27 14:48:30 +0100 | rekahsoft | (~rekahsoft@76.67.111.168) rekahsoft |
| 2026-02-27 13:39:24 +0100 | Enrico63 | (~Enrico63@host-80-104-109-187.retail.telecomitalia.it) Enrico63 |
| 2026-02-27 12:18:58 +0100 | Enrico63 | (~Enrico63@host-80-104-109-187.retail.telecomitalia.it) (Ping timeout: 240 seconds) |
| 2026-02-27 12:10:13 +0100 | kaskal | (~kaskal@2a02:8388:1a8b:7d00:6863:87bc:381d:11fa) kaskal |
| 2026-02-27 12:03:20 +0100 | tremon | (~tremon@83.80.159.219) tremon |
| 2026-02-27 11:44:35 +0100 | Enrico63 | (~Enrico63@host-80-104-109-187.retail.telecomitalia.it) Enrico63 |
| 2026-02-27 10:05:08 +0100 | werneta | (~werneta@71.83.160.242) (Quit: Lost terminal) |
| 2026-02-27 09:38:30 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) (Ping timeout: 246 seconds) |
| 2026-02-27 09:34:20 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) ChubaDuba |
| 2026-02-27 09:31:14 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) (Ping timeout: 248 seconds) |
| 2026-02-27 09:26:53 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) ChubaDuba |
| 2026-02-27 09:26:36 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) (Client Quit) |
| 2026-02-27 09:22:36 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) ChubaDuba |
| 2026-02-27 09:20:29 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) (Client Quit) |
| 2026-02-27 09:19:30 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) ChubaDuba |
| 2026-02-27 06:16:05 +0100 | werneta | (~werneta@71.83.160.242) werneta |
| 2026-02-27 05:21:00 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) (Ping timeout: 255 seconds) |
| 2026-02-27 05:16:43 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) ChubaDuba |
| 2026-02-27 04:43:06 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) (Quit: WeeChat 4.8.1) |
| 2026-02-27 03:29:55 +0100 | haskellbridge | (~hackager@96.28.224.214) hackager |
| 2026-02-27 03:29:20 +0100 | haskellbridge | (~hackager@96.28.224.214) (Remote host closed the connection) |
| 2026-02-27 02:53:20 +0100 | stackdroid18 | (~stackdroi@user/stackdroid) () |
| 2026-02-27 01:21:40 +0100 | tremon | (~tremon@83.80.159.219) (Quit: getting boxed in) |
| 2026-02-27 01:17:57 +0100 | werneta | (~werneta@71.83.160.242) (Ping timeout: 265 seconds) |
| 2026-02-27 00:09:27 +0100 | gwentpl | (~gwpl@user/gwentpl) gwentpl |
| 2026-02-27 00:09:00 +0100 | gwentpl | (~gwpl@user/gwentpl) (Quit: ZNC 1.10.1 - https://znc.in) |
| 2026-02-26 22:57:33 +0100 | ChubaDuba | (~ChubaDuba@5.165.179.216) ChubaDuba |
| 2026-02-26 22:47:48 +0100 | Ging | (46fea76d80@2001:bc8:1210:2cd8::470) |
| 2026-02-26 22:36:14 +0100 | redgloboli | (~redglobol@user/redgloboli) redgloboli |
| 2026-02-26 22:35:37 +0100 | redgloboli | (~redglobol@user/redgloboli) (*.net *.split) |
| 2026-02-26 22:29:42 +0100 | Ging | (46fea76d80@2001:bc8:1210:2cd8::470) (Ping timeout: 268 seconds) |
| 2026-02-26 22:28:24 +0100 | terrorjack | (~terrorjac@2a01:4f8:271:2d98::2) terrorjack |
