Wez Furlong f0e94084d1 change backspace/delete handling ... Previously we would try to pass through the Backspace and Delete code points without interference, but that behavior wasn't quite right. With this commit our behavior is now: - At the window layer: Classify a `Backspace` key press as logically `BS` and a `Delete` key press as logically `DEL` unless the `swap_backspace_and_delete` is true (macOS is true by default), in which case `Backspace` is mapped to `Delete` and vice versa. - At the terminal input layer: A `Backspace` input from the Window sends the `DEL` sequence to the pty as that matches the default `VERASE` stty configuration. A `Delete` input from the Window emits `\033[3~`, which matches up to the `TERMINFO` for `xterm-256color` which we claim to be compatible with, and is our default `$TERM` value. The net result of this is that `Backspace` will now start to emit `^?` which should match folks stty verase. Heads up to @fanzeyi! I've tested this only on a linux system so far and will follow up on a macOS system a little later today. Refs: https://github.com/wez/wezterm/issues/88 Refs: https://github.com/wez/wezterm/issues/63		2019-12-30 08:14:20 -08:00
..
src	change backspace/delete handling	2019-12-30 08:14:20 -08:00
Cargo.toml	failure -> anyhow + thiserror	2019-12-14 21:43:05 -08:00