Newest at the top
| 2026-03-13 11:40:58 +0100 | Enrico63 | (~Enrico63@host-82-61-84-117.retail.telecomitalia.it) (Ping timeout: 240 seconds) |
| 2026-03-13 11:26:25 +0100 | Enrico63 | (~Enrico63@host-82-61-84-117.retail.telecomitalia.it) Enrico63 |
| 2026-03-13 09:01:49 +0100 | vados | (~vados@46-133-183-219.mobile.vf-ua.net) |
| 2026-03-13 05:58:05 +0100 | vados | (~vados@46-133-140-234.mobile.vf-ua.net) (Ping timeout: 245 seconds) |
| 2026-03-13 04:15:11 +0100 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.8.1) |
| 2026-03-13 04:08:21 +0100 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2026-03-13 04:05:39 +0100 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2026-03-13 04:05:19 +0100 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2026-03-13 04:04:52 +0100 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2026-03-13 04:04:42 +0100 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2026-03-13 04:01:27 +0100 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2026-03-13 03:58:47 +0100 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2026-03-13 03:53:36 +0100 | terrorjack | (~terrorjac@2a01:4f8:271:2d98::2) terrorjack |
| 2026-03-13 02:54:48 +0100 | ml| | (~ml|@user/ml/x-5298235) (Client Quit) |
| 2026-03-13 02:53:50 +0100 | ml| | (~ml|@user/ml/x-5298235) ml| |
| 2026-03-13 02:07:54 +0100 | terrorjack | (~terrorjac@2a01:4f8:271:2d98::2) (Quit: The Lounge - https://thelounge.chat) |
| 2026-03-13 01:35:55 +0100 | werneta_ | (~werneta@71.83.160.242) werneta |
| 2026-03-13 00:57:24 +0100 | ml| | (~ml|@user/ml/x-5298235) (Quit: WeeChat 4.4.2) |
| 2026-03-12 22:09:37 +0100 | <haskellbridge> | <iqubic (she/her)> Cool beans! |
| 2026-03-12 22:02:43 +0100 | <geekosaur> | (xset's parameter parsing is idiosyncratic and primitive) |
| 2026-03-12 22:02:25 +0100 | <geekosaur> | e.g. xset r 500 50 |
| 2026-03-12 21:57:38 +0100 | <haskellbridge> | <iqubic (she/her)> Yes, I saw how to turn it on. Is there a way to manually change the other two values without completely killing X? |
| 2026-03-12 21:57:04 +0100 | <haskellbridge> | <iqubic (she/her)> auto repeat: on, auto repeat delay: 660, repeat rate: 25 |
| 2026-03-12 21:56:39 +0100 | <geekosaur> | I told you how to turn it on earlier |
| 2026-03-12 21:56:28 +0100 | <geekosaur> | yes |
| 2026-03-12 21:56:14 +0100 | <haskellbridge> | <iqubic (she/her)> The WINE thing is new to me though. Is there a way to change the autorepeat settings with xset? |
| 2026-03-12 21:55:13 +0100 | <haskellbridge> | <iqubic (she/her)> I know that. I switched to the TTY to check if key repeat being broken was a hardware thing or a software thing. |
| 2026-03-12 21:54:28 +0100 | <geekosaur> | wine might possibly disable or more likely take over key repeat |
| 2026-03-12 21:54:14 +0100 | <geekosaur> | right, tty and X11 (and wayland) key repeats are distinct, with different settings |
| 2026-03-12 21:51:55 +0100 | <haskellbridge> | <iqubic (she/her)> The last thing I remember doing before it broke was running a SNES emulator with WINE. |
| 2026-03-12 21:48:26 +0100 | <haskellbridge> | <iqubic (she/her)> I don't know what caused this issue, but I do remember switching to a TTY and seeing that key repeat worked there. And then I rebooted my machine, and things went back to normal. |
| 2026-03-12 17:30:00 +0100 | vados | (~vados@46-133-140-234.mobile.vf-ua.net) |
| 2026-03-12 17:27:13 +0100 | Digitteknohippie | Digit |
| 2026-03-12 15:56:48 +0100 | Digit | (~user@user/digit) (Ping timeout: 264 seconds) |
| 2026-03-12 15:56:38 +0100 | Digitteknohippie | (~user@user/digit) Digit |
| 2026-03-12 10:24:48 +0100 | vados | (~vados@46-133-140-234.mobile.vf-ua.net) (Ping timeout: 246 seconds) |
| 2026-03-12 09:06:51 +0100 | Enrico63 | (~Enrico63@host-82-61-84-117.retail.telecomitalia.it) (Quit: Client closed) |
| 2026-03-12 08:59:33 +0100 | Enrico63 | (~Enrico63@host-82-61-84-117.retail.telecomitalia.it) Enrico63 |
| 2026-03-12 07:28:41 +0100 | vados | (~vados@46-133-140-234.mobile.vf-ua.net) |
| 2026-03-12 06:58:05 +0100 | vados | (~vados@46-133-57-88.mobile.vf-ua.net) (Ping timeout: 252 seconds) |
| 2026-03-12 03:58:20 +0100 | <geekosaur> | (if I got the math right) |
| 2026-03-12 03:58:11 +0100 | <geekosaur> | (fwiw the repeat delay is in ms. if it somehoww got set to MAX_INT, that's around 23 days) |
| 2026-03-12 03:43:28 +0100 | <geekosaur> | it's also possible that the repeat delay is set really high (like, minutes or even hours) or that the repeat mask has been cleared somehow (all 0s in "auto repeating keys", which is likely to be rather difficult to fix) |
| 2026-03-12 03:33:59 +0100 | <geekosaur> | (or "xset q" to see what the settings including key repeat settings are) |
| 2026-03-12 03:33:34 +0100 | <geekosaur> | try: xset r on |
| 2026-03-12 03:15:08 +0100 | <haskellbridge> | Is there something wrong with my laptop and/or my Linux settings? |
| 2026-03-12 03:15:05 +0100 | <haskellbridge> | <iqubic (she/her)> So, for some reason, my laptop's built-in keyboard has stopped doing key-repeat. No matter how much I hold down a key, Linux only ever registers it a single time. |
| 2026-03-12 00:21:47 +0100 | stackdroid18 | (~stackdroi@user/stackdroid) () |
| 2026-03-11 21:45:54 +0100 | scardinal | (~supreme@0x573d64a9.static.cust.fastspeed.dk) (Quit: leaving) |
| 2026-03-11 21:42:14 +0100 | <geekosaur> | resizing it manually afterward eorked fine, but next time you started your X session it would do it again |