Bug 25497 - [typing] Finish Statement action [code manipulation]
Summary: [typing] Finish Statement action [code manipulation]
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 2.1   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2002-10-29 11:41 EST by Scott Rutledge CLA
Modified: 2007-06-22 10:01 EDT (History)
1 user (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 Scott Rutledge CLA 2002-10-29 11:41:08 EST 
This action would automatically close all open parenthesis on the current line, insert the semi-colon, and move to the next line.

Eg.
someMethod(someOtherMethod(param1<FINISH STATEMENT>
would result in:
someMethod(someOtherMethod(param1));
<CURSOR>

On an empty line (ws only), it would close the current block, and move the cursor to the next line, indenting appropriately.

A good shortcut for this action would be Ctrl+Enter.
Comment 1 Claude Knaus CLA 2002-10-31 05:27:00 EST 
Martin, wouldn't this be a quick fix candidate?
Comment 2 Scott Rutledge CLA 2002-11-04 12:19:41 EST 
I'm not sure Quick Fix would quite fit with the work-flow I intended. Quick Fix is an afer-the-fact operation, while this would be performed inline with entering new code. The purpose of this function would be to simplify creating deeply nested expressions that result in a high number of closing parenthesis. This would allow to user to avoid having to manually determine how many to close.
Comment 3 Martin Aeschlimann CLA 2002-11-12 10:29:17 EST 
This is not a quick fix operation, I agree with you. I doesn't fit to code 
assist (CTRL + SPACE) neither. Maybe like auto indent.
Comment 4 Dirk Baeumer CLA 2002-11-20 08:44:02 EST 
I agree that this souldn't be handled by quick fix. IMO it is more a smart 
editing feature. 

Moving to JDT Text for commenting.
Comment 5 Scott Rutledge CLA 2003-03-31 23:34:25 EST 
With 2.1 out, could this one be looked at again?
Comment 6 Dani Megert CLA 2007-02-09 10:57:05 EST 
No plans to work on this.
Comment 7 Dani Megert CLA 2007-06-22 09:59:13 EDT 
Get rid of deprecated state.