2026/03/09

2026-03-09 00:57:04 +0100stackdroid18(~stackdroi@user/stackdroid) ()
2026-03-09 01:10:37 +0100tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2026-03-09 03:56:24 +0100ml|(~ml|@user/ml/x-5298235) (Ping timeout: 255 seconds)
2026-03-09 04:09:30 +0100ml|(~ml|@user/ml/x-5298235) ml|
2026-03-09 07:22:04 +0100terrorjack(~terrorjac@2a01:4f8:271:2d98::2) terrorjack
2026-03-09 09:18:44 +0100ft(~ft@p4fc2a98c.dip0.t-ipconnect.de) (Quit: leaving)
2026-03-09 09:54:53 +0100ChubaDuba(~ChubaDuba@79.136.178.40) ChubaDuba
2026-03-09 09:56:09 +0100ChubaDuba(~ChubaDuba@79.136.178.40) (Client Quit)
2026-03-09 11:47:26 +0100T_X_(~T_X@diktynna.open-mesh.org) (Read error: Connection reset by peer)
2026-03-09 11:48:32 +0100T_X(~T_X@2a01:4f8:241:fc1:136:243:236:17) T_X
2026-03-09 12:55:57 +0100ChubaDuba(~ChubaDuba@79.136.178.40) ChubaDuba
2026-03-09 12:57:21 +0100ChubaDuba(~ChubaDuba@79.136.178.40) (Client Quit)
2026-03-09 15:01:45 +0100 <haskellbridge> <e​ldritchcookie> hello is there an easy way to have a NamedScratchpad behave as a full screen window? i tried to use doFullFloat for the hook but it covers my status bar, in the vertical direction goes a little outside the screen and in the horizontal direction it doesn't reach the end of the screen
2026-03-09 15:26:54 +0100vados(~vados@46-133-51-198.mobile.vf-ua.net)
2026-03-09 15:48:30 +0100Digit(~user@user/digit) (Ping timeout: 245 seconds)
2026-03-09 15:48:45 +0100Digitteknohippie(~user@user/digit) Digit
2026-03-09 16:24:20 +0100Digitteknohippie(~user@user/digit) (Ping timeout: 268 seconds)
2026-03-09 16:25:49 +0100 <geekosaur> that sounds like a bug in doFullFloat
2026-03-09 16:26:00 +0100 <geekosaur> I can't check now
2026-03-09 16:27:35 +0100tremon(~tremon@83.80.159.219) tremon
2026-03-09 16:31:19 +0100 <geekosaur> hm, actually I don't think it can be doFullFloat itself that's buggy, it just specifies a RationalRect 0 0 1 1
2026-03-09 16:32:22 +0100 <geekosaur> so either that is somehow being mistranslated to physical coordinates, or the program whose window you are adjusting has its own ideas (I have, sadly, seen this and needed to nuke its state/config file to fix, but it's thankfully rare)
2026-03-09 17:15:37 +0100Digit(~user@user/digit) Digit
2026-03-09 17:22:59 +0100DigitDigitteknohippie
2026-03-09 17:23:46 +0100DigitteknohippieDigit
2026-03-09 19:35:01 +0100vados(~vados@46-133-51-198.mobile.vf-ua.net) (Read error: Connection reset by peer)
2026-03-09 19:39:35 +0100vados(~vados@46-133-51-198.mobile.vf-ua.net)
2026-03-09 21:26:23 +0100stackdroid18(~stackdroi@user/stackdroid) stackdroid
2026-03-09 21:40:10 +0100stackdroid18(~stackdroi@user/stackdroid) ()
2026-03-09 21:45:03 +0100stackdroid18(~stackdroi@user/stackdroid) stackdroid
2026-03-09 21:55:39 +0100stackdroid18(~stackdroi@user/stackdroid) ()
2026-03-09 21:59:27 +0100stackdroid18(~stackdroi@user/stackdroid) stackdroid
2026-03-09 22:10:49 +0100stackdroid18(~stackdroi@user/stackdroid) ()