Skip to content

fix(config): remove home/end from messages_first/messages_last defaults#15246

Open
nathannewyen wants to merge 1 commit intoanomalyco:devfrom
nathannewyen:fix/home-end-keybind-conflict
Open

fix(config): remove home/end from messages_first/messages_last defaults#15246
nathannewyen wants to merge 1 commit intoanomalyco:devfrom
nathannewyen:fix/home-end-keybind-conflict

Conversation

@nathannewyen
Copy link
Contributor

Issue for this PR

Closes #14899

Type of change

  • Bug fix
  • New feature
  • Refactor / code improvement
  • Documentation

What does this PR do?

home and end keys were bound to both message navigation (messages_first, messages_last) and input cursor movement (input_buffer_home, input_buffer_end). The message bindings always took precedence, so home/end never worked in the input field.

Removed home/end from messages_first/messages_last defaults. Users still have ctrl+g and ctrl+alt+g for message navigation.

How did you verify your code works?

Tested locally — home/end now correctly move the cursor in the input field, and ctrl+g/ctrl+alt+g still navigate messages.

Screenshots / recordings

N/A — no UI change, only keybinding behavior fix.

Checklist

  • I have tested my changes locally
  • I have not included unrelated changes in this PR

home and end keys were bound to both message navigation
(messages_first, messages_last) and input cursor movement
(input_buffer_home, input_buffer_end). The message bindings
took precedence, preventing home/end from working in the input.

Closes anomalyco#14899
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"home" and "end" keys are bound twice

1 participant