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

Bug 352532

Summary:	[typing] Indenter should honor 'Indent on column'
Product:	[Eclipse Project] JDT	Reporter:	Ayushman Jain <amj87.iitr>
Component:	Text	Assignee:	JDT-Text-Inbox <jdt-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	minor
Priority:	P3	CC:	daniel_megert, deepakazad
Version:	3.7
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:	stalebug

Description Ayushman Jain

2011-07-20 02:47:15 EDT

BETA_JAVA7

The indenter currently does not respect the formatter's indentation settings for multi-catch that was added in bug 349314.

class MultiCatch {
    void foo() {
        try {
            throw new FileNotFoundException();
        } catch (FileNotFoundException | IOException | RuntimeException |
ArrayIndexOutOfBoundsException | IllegalArgumentException ex) {
        }
    }

}

Choose formatter>Line wrapping>Statements>catch "Indendation settings" as "Indent on column" and line wrapping as every element on new line.
Format the above code. Now use CTRL+I.

Comment 1 Deepak Azad

2011-07-20 03:11:09 EDT

The indenter works same as formatter as long as the formatter uses 'default indentation'.

Comment 2 Dani Megert

2011-07-20 05:19:07 EDT

Currently the indenter doesn't honor this in most cases, not just for multi-catch.

Comment 3 Eclipse Genie

2019-12-31 15:20:30 EST

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.

Comment 4 Eclipse Genie

2021-12-24 14:09:15 EST

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.