Bug 255838 - [typing] add Ctrl-q (quote-insert)
Summary: [typing] add Ctrl-q (quote-insert)
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4.1   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-19 11:57 EST by Daniel B. CLA
Modified: 2019-09-06 16:07 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel B. CLA 2008-11-19 11:57:09 EST
Build ID: M20080911-1700

In Emacs key bindings mode, add a binding of Control-q to an equivalent
of Emac's quote-insert function.

This is a key Emacs function controlling the editor to make it
"just do it" when the user just wants to insert a character instead 
of having the editor do whatever extra it usually does when that 
character is typed (e.g., special new-line handling, tabbing/indenting, 
etc.)


More information:

One example use is forcibly inserting a tab character where Eclispe
would normally take a TAB keystroke as an Indent Line command.


Another is, say, suppressing Eclipse's automatic breaking of string
literals when Return is pressed (e.g., if you really just want to 
throw the text after the insertion cursor onto the next line 
temporarily to concentrate on the first part of the text).

(If that sounds too trival or too special-case:  Remember that the 
first job of an editor is to be an editor--that is, to let the user
edit the text into the form the user wants.  Even if it provides
fancy features that help most of the time, it should still provide
an escape mechanism for direct control of the text.)
Comment 1 Olivier Thomann CLA 2008-11-19 11:58:40 EST
Move to JDT/UI
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:07:37 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.