Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 330741

Summary:	Wrong Behavior for "Run Last Launched External Tool" Key Binding
Product:	[Eclipse Project] Platform	Reporter:	Christopher Dalton <csmartdalton>
Component:	Ant	Assignee:	Platform-Ant-Inbox <platform-ant-inbox>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	minor
Priority:	P3	CC:	aleherb+eclipse, cdtdoug, csmartdalton, Michael_Rennie, rene.semmelrath
Version:	3.6
Target Milestone:	---
Hardware:	PC
OS:	Linux
Whiteboard:	stalebug

Description Christopher Dalton

2010-11-20 11:59:29 EST

Build Identifier: 20100917-0705

It appears that when I assign a key binding to the "Run Last Launched External Tool" command, the key actually invokes the "External Tools..." command.

Reproducible: Always

Steps to Reproduce:
1. Create an external tool configuration (ls -l works fine) and run it
2. Assign a key binding to "Run Last Launched External Tool" (i.e. Ctrl+F5)
3. Mouse over the external tools toolbar icon and verify the tooltip says "Run ls -l (Ctrl+F5)"
4. Click the icon and verify it launches ls -l
5. Push the key binding. It will open the external tools configurations window instead of launching the external tool.

Comment 1 Anton Leherbauer

2010-11-22 03:29:08 EST

External Tools is a platform feature.

Comment 2 Rene Semmelrath

2014-10-20 09:01:50 EDT

Have the something on Windows:
'Run Last Launched External Tool' runs 'External Tools Configurations'
the bug is decribed here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=322688

The thing is that a Keybinding with "Ctrl + Return" or "Ctrl + Numpad_Enter"
triggers the wrong behaviour. 

Keybindings wihtout Enter work as expected.

Unfortunately "Crtl + Return" is often used to trigger Build-Processes or evaluations with External Tools

Comment 3 Lars Vogel

2019-11-27 07:44:25 EST

This bug hasn't had any activity in quite some time. Maybe the problem got
resolved, was a duplicate of something else, or became less pressing for some
reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it.
The information can be, for example, that the problem still occurs, that you
still want the feature, that more information is needed, or that the bug is
(for whatever reason) no longer relevant.

If the bug is still relevant, please remove the stalebug whiteboard tag.