Bug 345476

Summary:	Ctrl+Alt+Space behaves like Ctrl+Space
Product:	[Applications] konsole	Reporter:	Moritz Bunkus <kde>
Component:	keyboard	Assignee:	Konsole Developer <konsole-devel>
Status:	RESOLVED FIXED
Severity:	normal	CC:	a.samirh78, cfeck, egmont, kde
Priority:	NOR
Version:	master
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Moritz Bunkus 2015-03-24 14:29:46 UTC

This is konsole @ git revision 9f8d3933940744cf8eca50d57558bfac82eb0ee7.

Pressing Ctrl+Space works just fine, as does Alt+Space. However, pressing Ctrl+Alt+Space sends the same keycode(s) as Ctrl+Space does. I'm pretty sure that the konsole in KDE 4.x did not have this limitation, and yes, there are applications that use this combination (Emacs for mark-sexp).

Running »cat« shows the following:

- for Ctrl+Space: ^@
- for Alt+Space: ^[  (with a trailing space)
- for Ctrl+Alt+Space: ^@

Reproducible: Always

Steps to Reproduce:
1. Run »emacs -nw« in konsole
2. Press Ctrl+Alt+Space
3. Emacs will show the message "mark set" instead of actually marking the sexp at point.

Actual Results:  
See description for all the details.

Comment 1 Moritz Bunkus 2015-03-24 14:58:52 UTC

In Emacs there's a secondary key binding for mark-sexp: Ctrl+Alt+@. This doesn't work in current konsole either.

I've re-installed konsole from KDE 4.14.6, and both combinations (Ctrl+Alt+Space and Ctrl+Alt+@) work just fine there.

Seems to be a general problem, not just with a single combination (and Ctrl+Space was fixed only three commits ago itself…).

Comment 2 Ahmad Samir 2018-03-03 20:24:09 UTC

You can fine tune the escape sequences sent by key combos using the konsole key bindings editor. Did you try that?

Comment 3 Egmont Koblinger 2018-03-04 10:51:05 UTC

For me, Ctrl+Alt+Space generates ^[^@ (that is, 0x1B 0x00) in konsole 17.04.3, just as in xterm and vte. I guess the bug's been fixed since it was reported.

Comment 4 Ahmad Samir 2018-03-04 12:09:57 UTC

Indeed it's been fixed. Thanks.

Feel free to reopen if you can still reproduce this issue.