| Summary: | [Key Bindings] vi keymap | ||
|---|---|---|---|
| Product: | [Eclipse Project] Platform | Reporter: | Michael Rieser <mike> |
| Component: | UI | Assignee: | Platform-UI-Inbox <Platform-UI-Inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | enhancement | ||
| Priority: | P3 | CC: | arthur.eclipse, eduardo_pereira |
| Version: | 2.0 | Keywords: | helpwanted |
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Whiteboard: | |||
|
Description
Michael Rieser
We will be unable to address this for 2.0. Although we now support the definition of key maps (by extension, not by the user), we will only have rudimentary support for emacs for 2.0, not vi. The underlying mechanisms do not support the modes required to do vi emulation. Defering to v3 for consideration of improving these mechanisms. Tight integration with an existing vi editor which supports OLE is also interesting, but of course will only work on Windows. We are unlikely to do this ourselves. This would be an excellent opportunity for you or someone else in the open source community to contribute to eclipse. Reopen for investigation It was reopened as part of a PR administration pass. Unfortunately the fact that it was reopened doesn't mean anything special. If there is time, it may be investigated. Eclipse will open OLE documents inplace (ex. .doc, .ppt) OLE controls may be used in a custom editor/view (See the SWT html browser example) this is not a key bindings issue anymore - key bindings can be fully customized but vi emulation requires special support from the editor. closing this pr - best step is to try and lobby vi emulation to the draft proposal. |