bugfix #7 : delete useless "k" and "j" char in manual mode, indeed "…

[kenyhenry]

bugfix #7 : delete "k" and "j" char indeed "up" and "down" is enough.

[Copilot]

Pull request overview

This PR aims to fix issue #7 in the connection dialog’s manual input mode by ensuring certain keys (notably j/k) are not consumed as navigation shortcuts, so they can be typed as normal characters.

Changes:

• Removed j/k handling from connection dialog navigation so those characters can be entered in manual mode.
• Minor formatting-only adjustments (alignment/spacing) in a few places.

Comments suppressed due to low confidence (1)

internal/app/app.go:3284

• In manual mode, the "/" key is still intercepted by case "/", "ctrl+f" and the handler returns without delegating to connectionDialog.Update, which means users still can’t type "/" (part of issue #7). Similarly, up/down are consumed even in manual mode. Consider only handling these keys in discovery mode and delegating to the text input when ManualMode is true.

	case "/", "ctrl+f":
		// Enter search mode (only in discovery mode)
		if !a.connectionDialog.ManualMode {
			a.connectionDialog.EnterSearchMode()
		}
		return a, nil

	case "up":
		if !a.connectionDialog.ManualMode {
			a.connectionDialog.MoveSelection(-1)
		}
		return a, nil

	case "down":
		if !a.connectionDialog.ManualMode {
			a.connectionDialog.MoveSelection(1)
		}
		return a, nil

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[tianzhou]

LGTM. Thanks for the contribution.