Bug 29336 - Additional editor actions needed
Summary: Additional editor actions needed
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Kai-Uwe Maetzel CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-01-11 12:52 EST by Todd Hill CLA
Modified: 2019-09-06 16:08 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Todd Hill CLA 2003-01-11 12:52:33 EST
Having switched to Eclipse from both MS Visual Studio and Visual Cafe' myself and many other users have become spoiled with some of the Brief editor capabilities.  Eclipse has many in M4+ (-very- nice btw) but could stand a couple more actions & capabilities :

 a) Center cursor in window,
 b) Make comment and uncomment move down one line when done,
 c) Delete previous/next word,
 d) Editor option to allow cursor to stay at a column while moving up and down, even if intervening lines are shorter,
 e) Allow a key binding to insert literal text,
 f) A single macro facility,
 g) Named, stored macros would be great too,
 h) Be able to save a named binding set,
 i) Be able to export/import key binding definitions.
Comment 1 Nick Edgar CLA 2003-01-13 13:45:06 EST
Need to separate the items that apply to the key bindings mechanism itself, and 
those that are specific actions that the text editor would need to provide.
Note that macro capabilities are mentioned in the 2.2 plan that was posted 
recently.
Comment 2 Chris McLaren CLA 2003-02-11 13:49:01 EST
a,b,c,d: are editor actions. moving to platform text for comment.

e,f,g: concern themselves with automating eclipse - this is proposed for 2.2 
already

h,i: key bindings can be exported and imported with your preference file.
Comment 3 Heath Borders CLA 2008-08-15 15:32:51 EDT
c, g, h, and i are all done now, right?
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:08:20 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. 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.