Walkthrough

Conditional checks in CSI (Control Sequence Introducer) handling were relaxed in input.go. The '_' case now applies Win32-like key mappings when P has elements, removing the intermediate-bytes-empty requirement. The '~' case similarly removed intermediate-bytes-empty constraints, processing when P has at least two elements and no LT prefix, broadening key mapping coverage.

Changes

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Areas requiring attention:

• Impact on CSI sequence parsing and how intermediate bytes affect routing to different handlers
• Verification that broadened conditions don't inadvertently capture unintended sequences
• Testing coverage for edge cases with various intermediate byte configurations
• Interaction with existing key mapping logic to ensure no regressions

Possibly related PRs

• chore: simplify the handling of the rxvt key codes #892: Modifies CSI parsing conditions and ordering in input.go for deciding when intermediates trigger key mapping versus other CSI handling paths.

Poem

🐰 A whisker-twitch of CSI delight,
Intermediate bytes no longer hold tight,
Keys map more freely, conditions now wide,
Win32-like sequences take their stride!
With broadened logic, we hop through with glee!

Pre-merge checks and finishing touches

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

#103

@ivanm696

I think this takes care of those cases:

	// this might have been an SS3 style key with modifiers applied
	if k, ok := ss3Keys[mode]; ok && P0 == 1 && len(P) > 1 {
		ip.post(NewEventKey(k, "", calcModifier(P[1])))
		return
	}