Johannes Altmanninger adb40149a3 Do not insert key's PUA encoding into the command line ... If a key's codepoint is in the PUA1 range, it could be either from our own named keys (like key::Space) or from a CSI u key that we haven't assigned a name yet https://sw.kovidgoyal.net/kitty/keyboard-protocol/#functional-key-definitions (The latter can still be bound using the \u1234 or the equivalent \e[4660u raw CSI u sequence.) It doesn't make sense to insert a PUA character into the commandline when the user presses PrintScreen; ignore them silently. This partially reverts b77d1d0e2 (Stop crashing on invalid Unicode input, 2024-02-27). That commit did: 1. convert input byte sequences that map to a PUA codepoint into several characters, using our on-char-per-byte PUA encoding. 2. do the same for inputs that are codepoints outside the valid Unicode range. 3. render them as replacement character (one per input byte) In future, we should probably remove these features altogether, and simply ignore invalid Unicode code points.		2024-04-09 00:46:16 +02:00
..
dir_iter.rs
encoding.rs
errors.rs
fileid.rs
gettext.rs	Make test_init() return a scope guard	2024-03-24 16:33:35 +01:00
mod.rs	Do not insert key's PUA encoding into the command line	2024-04-09 00:46:16 +02:00
printf.rs	Remove L! from sprintf calls	2024-01-13 08:52:54 +01:00
tests.rs	Make test_init() return a scope guard	2024-03-24 16:33:35 +01:00
wcstod.rs	Remove unnecessary scoped #[allow] attributes	2024-03-09 13:49:25 +01:00
wcstoi.rs	Remove using statements already imported by preludes	2024-02-28 09:41:51 -06:00