Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312157 - [UX] Eclipse is not keyboard-interactive enough - request for internal command-line.
Summary: [UX] Eclipse is not keyboard-interactive enough - request for internal comman...
Status: CLOSED WONTFIX
Alias: None
Product: e4
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 1.0   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Susan McCourt CLA
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-08 09:41 EDT by Pedro Rolo CLA
Modified: 2019-09-04 03:13 EDT (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Pedro Rolo CLA 2010-05-08 09:41:11 EDT 
Build Identifier: 

Old text editors/ide's like emacs and vi provide internal command lines, which allow users to execute/explore/define commands and keyboard shortcuts.

In a user interface prespective this allows to bridge begginer users (the ones who use the mouse for everything) and "guru-users" (the ones who only use keyboard shortcuts). It is a pitty that modern Ide's like emacs have droped such a valuable feature.

Reproducible: Always
Comment 1 Susan McCourt CLA 2010-05-08 18:06:23 EDT 
I don't see this happening in the context of 3.x, but I could see us exploring this in e4.
Comment 2 Pedro Rolo CLA 2010-05-09 09:42:24 EDT 
If implemented, plugins should be able to provide commands to this command line, of course.
Comment 3 Paul Webster CLA 2010-05-10 08:00:00 EDT 
In the meantime in 3.x there's QuickAssist (CTRL+3) that can execute commands (no composer support, however).

PW
Comment 4 Lars Vogel CLA 2019-09-04 03:13:18 EDT 
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 and remove the stalebug whiteboard tag. 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.

--