Newest at the top
| 2025-11-07 15:15:19 +0100 | ft | (~ft@p4fc2aaeb.dip0.t-ipconnect.de) ft |
| 2025-11-07 15:06:58 +0100 | hightower3 | (~hightower@dh207-112-105.xnet.hr) (Ping timeout: 244 seconds) |
| 2025-11-07 15:04:20 +0100 | hightower4 | (~hightower@dh207-112-200.xnet.hr) hightower2 |
| 2025-11-07 15:04:04 +0100 | _qw | (~eqw@user/eqw) eqw |
| 2025-11-07 14:47:17 +0100 | _qw | (~eqw@user/eqw) (Ping timeout: 260 seconds) |
| 2025-11-07 12:33:32 +0100 | Guest34 | (~Guest34@p200300ee97067ed843e1338c6ae2eb70.dip0.t-ipconnect.de) (Client Quit) |
| 2025-11-07 12:31:52 +0100 | Guest34 | (~Guest34@p200300ee97067ed843e1338c6ae2eb70.dip0.t-ipconnect.de) |
| 2025-11-07 09:28:23 +0100 | yecinem_ | (~yecinem@p200300ee0f2490006b0cdadfcd6535f6.dip0.t-ipconnect.de) |
| 2025-11-07 08:19:16 +0100 | ft | (~ft@p4fc2aaeb.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-11-07 04:52:21 +0100 | haskellbridge | (~hackager@96.28.224.214) hackager |
| 2025-11-07 04:51:35 +0100 | haskellbridge | (~hackager@96.28.224.214) (Remote host closed the connection) |
| 2025-11-07 04:36:21 +0100 | td_ | (~td@i5387093B.versanet.de) td_ |
| 2025-11-07 04:34:38 +0100 | td_ | (~td@i53870901.versanet.de) (Ping timeout: 256 seconds) |
| 2025-11-07 03:59:57 +0100 | hightower4 | (~hightower@cpe-94-253-245-24.st.cable.xnet.hr) (Ping timeout: 244 seconds) |
| 2025-11-07 03:57:18 +0100 | hightower3 | (~hightower@dh207-112-105.xnet.hr) hightower2 |
| 2025-11-07 02:18:08 +0100 | weitcis | (~quassel@172.91.73.15) |
| 2025-11-07 02:04:56 +0100 | weitcis | (~quassel@172.91.71.27) (Ping timeout: 265 seconds) |
| 2025-11-07 01:17:06 +0100 | hightower2 | (~hightower@213.186.15.36) hightower2 |
| 2025-11-06 21:21:45 +0100 | hightower3 | (~hightower@dh207-82-252.xnet.hr) (Ping timeout: 252 seconds) |
| 2025-11-06 21:19:19 +0100 | hightower4 | (~hightower@cpe-94-253-245-24.st.cable.xnet.hr) hightower2 |
| 2025-11-06 20:40:30 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) L29Ah |
| 2025-11-06 20:17:13 +0100 | L29Ah | (~L29Ah@wikipedia/L29Ah) (Read error: Connection reset by peer) |
| 2025-11-06 19:12:13 +0100 | ft | (~ft@p4fc2aaeb.dip0.t-ipconnect.de) ft |
| 2025-11-06 17:46:19 +0100 | yecinem_ | (~yecinem@p200300ee0f027400af0a7cdbe8524351.dip0.t-ipconnect.de) (Ping timeout: 250 seconds) |
| 2025-11-06 16:59:51 +0100 | <geekosaur> | (they don't take focus and use their own placement policy) |
| 2025-11-06 16:59:32 +0100 | <geekosaur> | that said, notification windows are unmanaged so I think it's mate-notification-daemon that has to do it itself |
| 2025-11-06 16:58:25 +0100 | <deebo> | hmm, mine doesnt, have to check if i'm properly extending the mateconfig |
| 2025-11-06 16:57:05 +0100 | <geekosaur> | deebo: mine already does, and I'm not doing anything special for it |
| 2025-11-06 14:02:07 +0100 | hightower2 | (~hightower@dh207-82-252.xnet.hr) (Ping timeout: 264 seconds) |
| 2025-11-06 13:58:47 +0100 | hightower3 | (~hightower@dh207-82-252.xnet.hr) hightower2 |
| 2025-11-06 13:55:15 +0100 | hightower2 | (~hightower@dh207-82-252.xnet.hr) hightower2 |
| 2025-11-06 13:54:56 +0100 | hightower2 | (~hightower@dh207-82-252.xnet.hr) (Remote host closed the connection) |
| 2025-11-06 13:28:44 +0100 | ChubaDuba | (~ChubaDuba@37.112.224.217) (Quit: WeeChat 4.7.1) |
| 2025-11-06 09:26:19 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Ping timeout: 250 seconds) |
| 2025-11-06 09:21:42 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) |
| 2025-11-06 09:18:11 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Client Quit) |
| 2025-11-06 09:16:25 +0100 | yecinem_ | (~yecinem@p200300ee0f027400af0a7cdbe8524351.dip0.t-ipconnect.de) |
| 2025-11-06 09:14:29 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) |
| 2025-11-06 08:54:22 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-11-06 08:52:25 +0100 | ft | (~ft@p4fc2aaeb.dip0.t-ipconnect.de) (Quit: leaving) |
| 2025-11-06 08:38:47 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) |
| 2025-11-06 08:38:05 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Quit: Ping timeout (120 seconds)) |
| 2025-11-06 08:33:39 +0100 | Solid | (~slot@xmonad/slotThe) (Quit: ERC 5.6.2-git (IRC client for GNU Emacs 31.0.50)) |
| 2025-11-06 08:27:13 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) |
| 2025-11-06 08:26:13 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Client Quit) |
| 2025-11-06 08:23:40 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) |
| 2025-11-06 08:21:16 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) (Quit: Client closed) |
| 2025-11-06 08:03:18 +0100 | <deebo> | "mate-notification-daemon" ~ _NET_WM_WINDOW_TYPE_NOTIFICATION |
| 2025-11-06 08:02:55 +0100 | <deebo> | using xmonad over mate desktop, can i somehow make notifications respect my panels like xmonad in general does? |
| 2025-11-06 07:57:34 +0100 | xjcj | (~xjcj@dslb-002-205-170-105.002.205.pools.vodafone-ip.de) |