08:27 <dnkl> msg ChanServ op #foot dnkl

08:27 <dnkl> bleh

08:28 <dnkl> 1.20.0 is out 🥳

09:40 <Arnavion> https://dgl.cx/2024/12/ghostty-terminal-title This got posted to HN yesterday. The tl;dr is that if a program sets the window title to an arbitrary shell command and then uses CSI 21 t (report window title) to echo it back and can somehow get that to appear in the input buffer of the shell when the user presses Enter, then that command gets executed

09:41 <Arnavion> So they want it to be disabled or at least disabled by default

09:44 <jpp1> happy new year 2025

09:56 <dnkl> Arnavion: https://codeberg.org/dnkl/foot/issues/1867

09:58 <dnkl> terminals can keep disabling features, but until shells do more proactive work to prevent this from happening, we're going to keep coming back to it

09:59 <Arnavion> Thanks. codeberg search had too many false results

10:03 <dnkl> we'll see where this goes - there's an issue open on the fish tracker

10:04 <dnkl> fwiw, I'm not adding an option. I'm just remove the escapes, if it comes to that

10:04 <dnkl> https://github.com/fish-shell/fish-shell/issues/10987

10:05 <dnkl> it should also be noted that there are lots of escapes that trigger a response from the terminal. the title report just happens to be one that's very easy to (miss-) use

10:06 <Arnavion> I can see that fish issue not getting fixed in that way, because too many people are used to queueing up the next command by typing while the current command is running, and that would break

10:09 <dnkl> yup, don't think so either. Just meant that now the issue has been raised. I have a feeling everybody has up until now just assumed this is something that can only be handled on the terminal side

10:09 <Arnavion> Yeah

10:27 <dnkl> Arnavion: follow up issue: https://codeberg.org/dnkl/foot/issues/1894

17:16 <bapt> m