Bug 65463 - [typing] Correct Indentation after ternary expr ( <stmt> ? <stmt> : <stmt;) incorrect
Summary: [typing] Correct Indentation after ternary expr ( <stmt> ? <stmt> : <stmt;) i...
Status: ASSIGNED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 normal with 5 votes (vote)
Target Milestone: ---   Edit
Assignee: JDT-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 102827 123485 137536 218857 265672 296938 344230 448850 471390 544373 544451 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-06-02 18:53 EDT by Omair-Inam Abdul-Matin CLA
Modified: 2022-09-19 11:34 EDT (History)
17 users (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 Omair-Inam Abdul-Matin CLA 2004-06-02 18:53:35 EDT 
I have the following snippet in my code

int numSegs =
     (i == (numTraj - 1))
     ? (leaf.m_children - leaf.m_startIdx.get(i))
     : (leaf.m_startIdx.get(i + 1) - leaf.m_startIdx.get(i));
     for (int j = 0; i < 3; i++) { // Correct indentation gives wrong indent
                    
     }
Doing a Ctrl + I on the for statement gives the incorrect indentation
Comment 1 Dani Megert CLA 2006-01-12 03:28:42 EST 
see also bug 123485
Comment 2 Tom Hofmann CLA 2006-04-19 12:46:59 EDT 
*** Bug 137536 has been marked as a duplicate of this bug. ***
Comment 3 x y CLA 2006-04-19 12:51:44 EDT 
This seems to be close to bug 130469.
Comment 4 Dani Megert CLA 2006-05-22 15:30:03 EDT 
*** Bug 102827 has been marked as a duplicate of this bug. ***
Comment 5 Tom Hofmann CLA 2006-08-14 09:38:24 EDT 
Moving back to inbox.
Comment 6 Tom Hofmann CLA 2006-09-22 10:02:44 EDT 
JavaHeuristicScannerTest contains two commented-out test cases for this. Once fixed, those should be enabled.
Comment 7 Dani Megert CLA 2007-03-29 05:11:55 EDT 
*** Bug 123485 has been marked as a duplicate of this bug. ***
Comment 8 Dani Megert CLA 2008-02-15 03:11:11 EST 
*** Bug 218857 has been marked as a duplicate of this bug. ***
Comment 9 Dani Megert CLA 2009-02-21 04:15:44 EST 
*** Bug 265672 has been marked as a duplicate of this bug. ***
Comment 10 Markus Keller CLA 2009-12-07 07:01:48 EST 
*** Bug 296938 has been marked as a duplicate of this bug. ***
Comment 11 Cameron Miller CLA 2010-09-15 20:14:07 EDT 
I also get this problem when editing C++ files. Do I need to raise a separate bug for this problem to fix it for C++?
Comment 12 Dani Megert CLA 2010-09-16 01:21:31 EDT 
(In reply to comment #11)
> I also get this problem when editing C++ files. Do I need to raise a separate
> bug for this problem to fix it for C++?
Yes, please.
Comment 13 Dani Megert CLA 2011-04-13 09:34:59 EDT 
Rajesh, do you still plan to provide a patch for this? If so, I'd need it by the end of this week.
Comment 14 Dani Megert CLA 2011-04-29 01:45:05 EDT 
*** Bug 344230 has been marked as a duplicate of this bug. ***
Comment 15 Dani Megert CLA 2015-07-21 12:22:09 EDT 
*** Bug 471390 has been marked as a duplicate of this bug. ***
Comment 16 Ricardo CLA 2015-11-10 10:26:45 EST 
If doing "Ctrl + I" when comparing content in "Team synchronizing" perspective, this works as expected (not in the normal editor)
Comment 17 Dani Megert CLA 2019-02-12 10:14:02 EST 
*** Bug 544373 has been marked as a duplicate of this bug. ***
Comment 18 Dani Megert CLA 2019-02-12 10:14:20 EST 
*** Bug 448850 has been marked as a duplicate of this bug. ***
Comment 19 Dani Megert CLA 2019-02-17 10:41:45 EST 
*** Bug 544451 has been marked as a duplicate of this bug. ***
Comment 20 Ezewuzie okafor CLA 2020-07-28 15:36:29 EDT 
I was about creating the same bug till I saw this. I am using the latest Eclipse and the error persists
Comment 21 Eclipse Genie CLA 2022-09-19 11:34: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.

--
The automated Eclipse Genie.