Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 321429

Summary: [typing] Semicolon automatically inserted at wrong place (for multi-line statement)
Product: [Eclipse Project] JDT Reporter: Jerry Mising name <commer>
Component: TextAssignee: JDT-Text-Inbox <jdt-text-inbox>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: daniel_megert, Olivier_Thomann
Version: 3.6   
Target Milestone: ---   
Hardware: All   
OS: All   
Whiteboard: stalebug
Attachments:
Description Flags
enable automatically insert semicolons
none
create a multi-line statement
none
type semicolon none

Description Jerry Mising name CLA 2010-07-31 07:12:43 EDT 
Build Identifier: 20100617-1415

For multiple line statement, semicolon is appended at the end of line cursor locates, rather than the end of the statement.

Reproducible: Always

Steps to Reproduce:
1. Turn on "Automatically insert at correct position" for "Semicolons".
2. Create a multi-line statement.
3. Move the cursor to a line that's not the last line, and type semicolon.
4. Notice the semicolon inserted.
Comment 1 Jerry Mising name CLA 2010-07-31 07:13:44 EDT 
Created attachment 175642 [details]
enable automatically insert semicolons
Comment 2 Jerry Mising name CLA 2010-07-31 07:19:53 EDT 
Created attachment 175644 [details]
create a multi-line statement

The "new Runnable" is generated by Content Assist. Cursor is located at Runnable(|).
Comment 3 Jerry Mising name CLA 2010-07-31 07:21:30 EDT 
Created attachment 175645 [details]
type semicolon

Cursor is located at Runnable(|) after Content Assist. Type semicolon and notice the ";" is inserted at the end of the line.
Comment 4 Olivier Thomann CLA 2010-08-01 10:25:06 EDT 
Moving to JDT/Text
Comment 5 Eclipse Genie CLA 2019-10-11 01:52:13 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.

--
The automated Eclipse Genie.