Ada
Ada
@AndydeCleyre My best guess is that it's reopening STDIN after it's closed from the pipe. Is there any way to handle that elegantly with plumbum, e.g., trying to reconnect after...
Ah, my apologies. :)
For context, I'm using Wezterm (20240203-110809-5046fc22). My Ctrl+Q keybindings still do not work, but Ctrl+C does, which is counter to my configuration.
I think it's just very common for applications that put the terminal in raw mode to hardcode Ctrl+C and call it a day. It sets a really bad precedent, IMO....
It doesn't seem too hard to detect terminal state and then decide which key to interpret as interrupt in raw mode based on that. I could write a mockup program...
Here's a minimal example: ```rs use std::io::{self, Read}; use std::os::unix::io::AsRawFd; use termios::*; fn main() { let stdin_fd = io::stdin().as_raw_fd(); let original_term_config = Termios::from_fd(stdin_fd).unwrap(); let interrupt_char = original_term_config.c_cc[VINTR]; let mut raw_termios...
Any progress on this?
This seems like a pretty simple feature to implement. Have a state directory (`~/.local/share/helix`) (de|)serialize with serde, and have trust remembered on a per-directory basis.
What about adding the next line down to the selection when the user hits 'x' again? How easy would that be to add via keybindings.json?
Seems very script-y. I imagine there must be some way to embed js into keybindings in VSCode?