Other win32-input-mode inconsistencies
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 7.5k
- Forks
- 353
- Avg merge
- 2d 11h
- Merged PRs (30d)
- 15
Description
When using win32-input-mode on Windows:
- function keys seem to lack key release events
- modifier events are not reported (meaning pressing control or shift by itself should generate events in this mode)
- (reported separately, so feel free to ignore here or close that issue in favor of this one) control-i is reported as tab
- No report to the XDA (extended DA) to provide the terminal name
I really really want to have a 3rd party terminal alternative for Windows (so I can recommend), as WezTerm and Alacritty are both absolutely terrible about these details. So far nothing seems to come close to touching Windows Terminal for correctness, but Rio comes closest of the options I've tried.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the Windows implementation of win32-input-mode and tracing how function keys, standalone modifiers, and terminal queries are encoded. Verify the behavior against the reported expectations: function-key release events and modifier events are emitted, and an XDA response provides the terminal name; control-I may be handled separately.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100