Summary: | Implement fixterms | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | ariasuni <aria> |
Component: | keyboard | Assignee: | Konsole Developer <konsole-devel> |
Status: | REPORTED --- | ||
Severity: | normal | CC: | unxed |
Priority: | NOR | ||
Version: | master | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
ariasuni
2021-04-20 20:48:58 UTC
Sorry I hit enter too early, I meant: Kitty implemented in *2021* a slightly different *version* who apparently fixes some problems with fixterms. Also see this comment about the «state of the art» of terminals: https://github.com/mawww/kakoune/issues/2554#issuecomment-436300959 There are also at least three other protocols for "raw keyboard" input in terminals. iTerm2 protocol https://gitlab.com/gnachman/iterm2/-/issues/7440#note_129307021 Windows Terminal's "win32-input-mode" https://github.com/microsoft/terminal/pull/6309 far2l terminal extensions https://github.com/elfmz/far2l/blob/master/WinPort/FarTTY.h The only one of them that already have some support in apps is far2l's one (apps supporting it are "turbo" text editor, "putty4far2l" putty fork, cyd01's "KiTTY"). It is tied to Windows keyboard codes, but translation from x11 codes is easy: https://github.com/unxed/xkb2win/ |