157523 2008-02-09 15:36:25 +0000 Kate terminal prevents shortcuts to work 2012-11-12 07:44:41 +0000 1 1 2 Applications kate general unspecified unspecified Linux RESOLVED WONTFIX NOR wishlist --- 1 brauliobo kwrite-bugs-null adaptee christoph divided.mind konsole-bugs-null linuxfever samjnaa http://commits.kde.org/kate/c0df718eb49f1b988067c656200bc74f5fa5b725 0 oldest_to_newest 578987 0 brauliobo 2008-02-09 15:36:25 +0000 Version: 3.0.1 (using 4.0.1 (KDE 4.0.1), Gentoo) Compiler: x86_64-pc-linux-gnu-gcc OS: Linux (x86_64) release 2.6.24-gentoo When using kate terminal (is has focus), its shortcut (for me Atl+1), and probably others, does not work anymore, so I cant hide the terminal using the same shortcut 580000 1 anderslund 2008-02-13 09:25:36 +0000 This is a problem with konsole 580588 2 robertknight 2008-02-15 19:48:20 +0000 This is related to Bug #157496 645585 3 brauliobo 2008-09-11 18:37:25 +0000 is this passive of fixing? maybe a hierarchy structure for the shortcuts... 645606 4 robertknight 2008-09-11 19:16:04 +0000 Hi, This is Kate's problem now. It needs to respond to the overrideShortcut() signal from the Konsole part and then set the override parameter to true or false to indicate whether the shortcut should be triggered or whether the key combination should be sent to the terminal instead. 863646 5 divided.mind 2009-11-17 15:05:51 +0000 *** Bug 169748 has been marked as a duplicate of this bug. *** 863659 6 divided.mind 2009-11-17 15:12:16 +0000 Currently some shortcuts work and some don't. Eg. ctrl+shift+f12 properly defocuses, but shift+f12 doesn't. This needs to either be fixed or properly documented; I'm not sure if this fits within the scope of this bug, though. Thoughts? 1002652 7 linuxfever 2010-08-13 10:34:34 +0000 I still have the same problem in KDE 4.5.0 -- kubuntu packages 1094644 8 linuxfever 2011-03-07 23:38:37 +0000 Same problem in 4.6.1 -- kubuntu packages 1105709 9 linuxfever 2011-04-08 20:35:50 +0000 Still in 4.6.2... 1175668 10 adaptee 2011-10-21 05:48:39 +0000 By default, konsole kpart sends all key combinations containing only one modifier(Shift/Ctrl/Alt) to the terminal process, thus overriding potential shortcut. So Alt+F doesn't work while Ctrl+Shift+F still works in kate. As Robert has said in comment #4, that behavior can be controlled by host apps by responding to the overrideShortcut(QKeyEvent*, bool&) signal. 1312014 11 christoph 2012-11-03 12:14:50 +0000 Git commit 861d7ed350f9e81d3e18d30d0aa6ca832ba9506d by Christoph Cullmann. Committed on 03/11/2012 at 13:14. Pushed by cullmann into branch 'master'. let konsole not eat half of all shortcuts M +13 -3 kate/plugins/konsole/kateconsole.cpp M +6 -0 kate/plugins/konsole/kateconsole.h M +10 -0 kate/plugins/project/kateprojectinfoviewterminal.cpp M +6 -0 kate/plugins/project/kateprojectinfoviewterminal.h http://commits.kde.org/kate/861d7ed350f9e81d3e18d30d0aa6ca832ba9506d 1312355 12 dhaumann 2012-11-04 13:16:02 +0000 I heavily used the reverse search in konsole through CTRL+R, which now is not possible anymore, as it now triggers search & replace. Any comments on that? ;) 1312356 13 christoph 2012-11-04 13:17:11 +0000 Then fix it and let it overwrite ctrl-r :P 1313980 14 christoph 2012-11-09 19:43:23 +0000 the overwrite control is sensefree, as there is no sane way to query the matching QKeyEvent for the user configured QAction QKeySequences, back to old behavior, some shortcuts shall not be used for console switching. 1313982 15 christoph 2012-11-09 19:44:30 +0000 Git commit c0df718eb49f1b988067c656200bc74f5fa5b725 by Christoph Cullmann. Committed on 09/11/2012 at 20:43. Pushed by cullmann into branch 'master'. let console eat shortcuts again we can't senseful match against QKeySequences of the terminal plugin actions Related: bug 309723 M +3 -3 kate/plugins/konsole/kateconsole.cpp M +3 -3 kate/plugins/project/kateprojectinfoviewterminal.cpp http://commits.kde.org/kate/c0df718eb49f1b988067c656200bc74f5fa5b725 1314720 16 dhaumann 2012-11-12 07:44:41 +0000 To show/hide the terminal quickly, you can bind a shortcut to "Show Terminal" in the "Configure Shortcuts" dialog. To switch focus, you can also use the "Focus Terminal" action. If you bind a shortcut to one of these and get used to it, this may be a good workaround for this issue, as like Christoph said, it's unfixable...