Git commit 1363cbc9f5f4eeece5068bfaafebf058b3c0040b by Kevin Funk. Committed on 22/03/2018 at 06:13. Pushed by kfunk into branch 'master'.
Reassign Debug Launch shortcut to Alt + F9 Summary: The was a key shortcut conflict between KatePart and KDevelop for the F9 key. Easily fixed by reassigning Debug Launch to Alt + F9. BUG: 386918 FIXED-IN: 5.3.0 Reviewers: #kdevelop, kdevelop-devel, brauch Reviewed By: #kdevelop, brauch Subscribers: brauch, kdevelop-devel, #kdevelop Tags: #kdevelop Differential Revision: https://phabricator.kde.org/D11431 M +2 -2 doc/kdevelop/index.docbook M +1 -1 kdevplatform/shell/runcontroller.cpp https://commits.kde.org/kdevelop/1363cbc9f5f4eeece5068bfaafebf058b3c0040b diff --git a/doc/kdevelop/index.docbook b/doc/kdevelop/index.docbook index 99066eccb4..e611d32624 100644 --- a/doc/kdevelop/index.docbook +++ b/doc/kdevelop/index.docbook @@ -1217,7 +1217,7 @@ template into &kdevelop; by opening the template manager, activating the appropr <entry>Run</entry> </row> <row> - <entry><keycap>F9</keycap></entry> + <entry><keycombo>&Alt;<keycap>F9</keycap></keycombo></entry> <entry>Run program in the debugger; you may want to set breakpoints beforehand, for example by right-clicking with the mouse on a particular line in the source code</entry> </row> </tbody> @@ -1228,7 +1228,7 @@ template into &kdevelop; by opening the template manager, activating the appropr </chapter> <chapter id="debugging-programs-in-kdevelop"><title>Debugging programs in &kdevelop;</title> <sect1 id="running-a-program-in-the-debugger"><title>Running a program in the debugger</title> -<para>Once you have a launch configured (see <link linkend="running-programs-in-kdevelop">Running programs</link>), you can also run it in a debugger: Select the menu item <menuchoice><guimenu>Run</guimenu><guimenuitem>Debug Launch</guimenuitem></menuchoice>, or hit <keycap>F9</keycap>. If you are familiar with <application>gdb</application>, the effect is the same as starting <application>gdb</application> with the executable specified in the launch configuration and then saying <varname>Run</varname>. This means that if the program calls <varname>abort()</varname> somewhere (⪚ when you run onto a failing assertion) or if there is a segmentation fault, then the debugger will stop. On the other hand, if the program runs to the end (with or without doing the right thing) then the debugger will not stop by itself before the program is finished. In the latter case, you will want to set a breakpoint on all those lines of your code base where you want the debugger to stop before you run the debug launch. You +<para>Once you have a launch configured (see <link linkend="running-programs-in-kdevelop">Running programs</link>), you can also run it in a debugger: Select the menu item <menuchoice><guimenu>Run</guimenu><guimenuitem>Debug Launch</guimenuitem></menuchoice>, or hit <keycombo>&Alt;<keycap>F9</keycap></keycombo>. If you are familiar with <application>gdb</application>, the effect is the same as starting <application>gdb</application> with the executable specified in the launch configuration and then saying <varname>Run</varname>. This means that if the program calls <varname>abort()</varname> somewhere (⪚ when you run onto a failing assertion) or if there is a segmentation fault, then the debugger will stop. On the other hand, if the program runs to the end (with or without doing the right thing) then the debugger will not stop by itself before the program is finished. In the latter case, you will want to set a breakpoint on all those lines of your code base where you want the debugger to stop before you run the debug launch. You can do that by moving the cursor on such a line and selecting the menu item <menuchoice><guimenu>Run</guimenu><guimenuitem>Toggle breakpoint</guimenuitem></menuchoice>, or right-clicking on a line and selecting <guilabel>Toggle Breakpoint</guilabel> from the context menu.</para> <para> <screenshot> diff --git a/kdevplatform/shell/runcontroller.cpp b/kdevplatform/shell/runcontroller.cpp index 79a91b2017..670b46bcd9 100644 --- a/kdevplatform/shell/runcontroller.cpp +++ b/kdevplatform/shell/runcontroller.cpp @@ -447,7 +447,7 @@ void RunController::setupActions() connect(d->runAction, &QAction::triggered, this, &RunController::slotExecute); d->dbgAction = new QAction( QIcon::fromTheme(QStringLiteral("debug-run")), i18n("Debug Launch"), this); - ac->setDefaultShortcut( d->dbgAction, Qt::Key_F9); + ac->setDefaultShortcut( d->dbgAction, Qt::ALT + Qt::Key_F9); d->dbgAction->setIconText( i18nc("Short text for 'Debug launch' used in the toolbar", "Debug") ); d->dbgAction->setToolTip(i18nc("@info:tooltip", "Debug current launch")); d->dbgAction->setStatusTip(i18n("Debug current launch"));
