2025/04/18

Newest at the top

2025-04-18 12:45:44 +0200catman(~catman@user/catman) catman
2025-04-18 12:43:39 +0200catman(~catman@user/catman) (Ping timeout: 260 seconds)
2025-04-18 11:49:29 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft
2025-04-18 11:38:22 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) (Quit: Lost terminal)
2025-04-18 11:18:23 +0200catman(~catman@user/catman) catman
2025-04-18 10:50:18 +0200catman(~catman@user/catman) (Ping timeout: 276 seconds)
2025-04-18 10:14:52 +0200chomwitt-alt(~chomwitt@2a02:587:7a07:1100:12c3:7bff:fe6d:d374)
2025-04-18 08:51:05 +0200werneta(~werneta@syn-071-083-160-242.res.spectrum.com) (Ping timeout: 260 seconds)
2025-04-18 08:40:40 +0200td_(~td@i5387091F.versanet.de)
2025-04-18 08:34:00 +0200td_(~td@i5387091F.versanet.de) (Quit: waking up from the american dream ...)
2025-04-18 08:14:32 +0200 <liskin> Strange that there are no warnings to be seen
2025-04-18 08:13:45 +0200 <liskin> geekosaur: yeah they probably do
2025-04-18 04:55:50 +0200werneta(~werneta@syn-071-083-160-242.res.spectrum.com) werneta
2025-04-18 04:31:06 +0200td_(~td@i5387091F.versanet.de)
2025-04-18 04:29:43 +0200td_(~td@i53870930.versanet.de) (Ping timeout: 272 seconds)
2025-04-18 04:14:30 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) hackager
2025-04-18 04:13:43 +0200haskellbridge(~hackager@syn-024-093-192-219.res.spectrum.com) (Remote host closed the connection)
2025-04-18 03:04:32 +0200 <geekosaur> hm. do our nix builds need to be updated? I'm getting complaints that the 20.04 runners no longer exist in my local fork
2025-04-18 01:13:52 +0200tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2025-04-18 00:20:20 +0200chomwitt-alt(~chomwitt@2a02:587:7a07:1100:12c3:7bff:fe6d:d374) (Ping timeout: 244 seconds)
2025-04-17 23:19:12 +0200Digit(~user@user/digit) Digit
2025-04-17 23:15:13 +0200Digit(~user@user/digit) (Remote host closed the connection)
2025-04-17 22:31:51 +0200Digit(~user@user/digit) Digit
2025-04-17 22:18:54 +0200Digit(~user@user/digit) (Ping timeout: 276 seconds)
2025-04-17 21:31:21 +0200_qw(~eqw@user/eqw) eqw
2025-04-17 21:24:10 +0200DigitteknohippieDigit
2025-04-17 21:21:21 +0200Digit(~user@user/digit) (Ping timeout: 248 seconds)
2025-04-17 21:19:57 +0200Digitteknohippie(~user@user/digit) Digit
2025-04-17 20:57:35 +0200chomwitt-alt(~chomwitt@2a02:587:7a07:1100:12c3:7bff:fe6d:d374)
2025-04-17 20:44:59 +0200_qw(~eqw@user/eqw) (Ping timeout: 268 seconds)
2025-04-17 20:28:39 +0200down200-(~down200@shell.lug.mtu.edu) (Ping timeout: 244 seconds)
2025-04-17 18:08:38 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) ft
2025-04-17 17:54:28 +0200_qw(~eqw@user/eqw) eqw
2025-04-17 17:47:27 +0200_qw(~eqw@user/eqw) (Ping timeout: 244 seconds)
2025-04-17 17:47:00 +0200L29Ah(~L29Ah@wikipedia/L29Ah) (Ping timeout: 252 seconds)
2025-04-17 17:38:01 +0200 <geekosaur> missed them…
2025-04-17 17:22:18 +0200Zevv(~Zevvvvv@not.connected.by.freedominter.net) ()
2025-04-17 17:11:54 +0200chomwitt-alt(~chomwitt@2a02:587:7a07:1100:12c3:7bff:fe6d:d374) (Ping timeout: 265 seconds)
2025-04-17 17:00:29 +0200 <Zevv> fixing with --left-of breaks the screen/workspace relationship
2025-04-17 17:00:22 +0200 <Zevv> after X restart I get the normal behavior, although my screens are in the wrong order
2025-04-17 16:46:06 +0200 <Zevv> so what's different now?
2025-04-17 16:46:03 +0200 <Zevv> on my other PCs this always worked as intended, where every display is one screen and the layouts are constrianed to their respective screens/desktops
2025-04-17 16:45:38 +0200 <Zevv> both screens make 1 desktop instead of 2
2025-04-17 16:45:26 +0200 <Zevv> but my layouts are spread out over two screens
2025-04-17 16:45:18 +0200 <Zevv> Hi all. I feel I should know these kind of things after 15 years of using xmonad, but apparently I do not. I connect a second screen to my PC, run `xrandr --output HDMI-A-0 --left-of DisplayPort-2 --auto` and it works
2025-04-17 16:44:34 +0200Zevv(~Zevvvvv@not.connected.by.freedominter.net)
2025-04-17 10:41:16 +0200chomwitt-alt(~chomwitt@2a02:587:7a07:1100:12c3:7bff:fe6d:d374)
2025-04-17 09:43:08 +0200ft(~ft@p4fc2a6e6.dip0.t-ipconnect.de) (Quit: leaving)
2025-04-17 08:20:36 +0200redgloboli(~redglobol@user/redgloboli) redgloboli
2025-04-17 08:12:01 +0200redgloboli(~redglobol@user/redgloboli) (Ping timeout: 265 seconds)