Repository navigation
Handle \EOM escape sequence as newline for Konsole compatibility #2115
Description
(🤖 Crafted in digital dialogue co-authored w/ AI, pondering why terminals still haunt us with 1978 ghosts...)
Problem
In KDE Konsole with "Default (XFree 4)" keyboard layout, pressing Shift+Enter sends \EOM (ESC O M, hex: 0x1B 0x4F 0x4D) instead of a newline. This is the VT100 escape sequence for numeric keypad Enter.
Current Behavior
- Press Shift+Enter in claude directly in Konsole (expecting to add a newline without sending the message)
- "OM" appears in the input field
- No newline is created
- User cannot create multi-line input
Expected Behavior
- Press Shift+Enter
- A newline is inserted for multi-line entry without sending the message
- User can continue typing on the next line
- Enter (without Shift) sends the complete multi-line message
Note
This issue is not visible when using tmux inside Konsole, as tmux intercepts and normalizes escape sequences, translating \EOM appropriately instead of displaying "OM".
Root Cause
Konsole's default keytab maps Return+Shift : "\EOM" due to legacy VT100 compatibility. This made sense when terminals had physical numeric keypads (1970s-1980s), but modern users expect Shift+Enter to insert newlines for multiline input.
Proposed Solution
Claude Code should interpret \EOM as a newline insertion (NOT message submission). This would:
- Fix the issue for all Konsole users without requiring terminal reconfiguration
- Maintain compatibility (no app legitimately expects
\EOMfrom Shift+Enter in 2025) - Avoid the pitfalls of terminal-specific keybinding modifications (see [BUG] iTerm2 keybinding for shift+enter breaks shift+enter in other programs running in iTerm2 #614)
- Allow multi-line input composition in Konsole
Code Change (pseudo-code)
// In input handling
if (inputSequence === '\x1B\x4F\x4D') { // \EOM
insertNewline(); // Add newline to input buffer, do NOT send message
}Benefits
- Works immediately for all Konsole users
- No terminal configuration required
- Doesn't break other applications (unlike terminal keybinding approach)
- Simple, focused fix for a specific escape sequence issue
Alternative Workaround
Users can manually fix by modifying Konsole's keytab (script available: https://gist.github.com/gwpl/e2f5a4ade2a3ef02a811b761c8993bc4), but this requires technical knowledge and per-user configuration.
Environment
- Terminal: KDE Konsole
- Keyboard Layout: Default (XFree 4)
- OS: Linux (KDE)
- Claude Code version: [affected in current version]
Related Issues
- Support shift+enter in most terminals #1758 (general Shift+Enter support)
- [BUG] iTerm2 keybinding for shift+enter breaks shift+enter in other programs running in iTerm2 #614 (terminal keybinding conflicts)
This would provide immediate relief for Konsole users while the longer-term Kitty protocol support (#1758) is being developed.
Activity
wolffiex commentedon Jun 17, 2025
sigh, terminal emulators are hard
gwpl commentedon Jun 18, 2025
@wolffiex Yes indeed, terminals are like many layers of the Matrix to go deeper! 🐇🕳️
Speaking of terminal magic, I just opened #2266 about bringing some visual sorcery to Claude Code - terminal graphics protocols (Sixel, Kitty, iTerm2). Because sometimes ASCII art just isn't enough when you need to see that matplotlib graph or system diagram right in your terminal!
Who knew that in 2025 we'd still be channeling the spirit of DEC VT340 terminals from the 80s? But hey, that's the beauty of terminals - they're both ancient scrolls and cutting-edge interfaces at the same time. ✨
DBosley commentedon Sep 14, 2025
Thank you @gwpl for that gist. This was bugging me a ton. Gotta love how ancient tech is still holding us back.
github-actions commentedon Dec 5, 2025
This issue has been inactive for 30 days. If the issue is still occurring, please comment to let us know. Otherwise, this issue will be automatically closed in 30 days for housekeeping purposes.
fanick1 commentedon Dec 7, 2025
I am not sure if this is the right workaround, but what I tried was changing the key binding in the Konsole settings:
Settings > Edit Current Profile... > Keyboard > Default(XFree 4) > Edit > filter for Return+Shift - change the \EOM to \n
(it might have some side effects elsewhere - like shift+enter suddenly submitting commands in normal shell - but so far so good)
github-actions commentedon Jan 8, 2026
This issue has been automatically closed due to 60 days of inactivity. If you're still experiencing this issue, please open a new issue with updated information.
github-actions commentedon Jan 15, 2026
This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.