Eclipse Community Forums: Java Development Tools (JDT) » Code formatter in M8: Preserve exisiting line breaks?

Home » Language IDEs » Java Development Tools (JDT) » Code formatter in M8: Preserve exisiting line breaks?

Code formatter in M8: Preserve exisiting line breaks? [message #154727]

Fri, 16 April 2004 17:01

Eclipse User

Hi all,

There was a "Preserve existing line breaks" option in the code formatter in
M7, which seems to have disappeared in M8. I notice that someone filed bug
54667, requesting such a feature, and that has been deferred to post 3.0.

I wasn't able to find any explanation of why it was removed, and I was
hoping that someone could clue me in.

Thanks for your help.

Cheers,
Dave

Re: Code formatter in M8: Preserve exisiting line breaks? [message #154895 is a reply to message #154727]

Mon, 19 April 2004 09:44

Eclipse User

Originally posted by: olivier_thomannNO.ca.ibm.comSPAM

Le Fri, 16 Apr 2004 17:01:55 -0400, Dave Steinberg
<davidms@ca.ibm.com> a écrit :
>There was a "Preserve existing line breaks" option in the code formatter in
>M7, which seems to have disappeared in M8. I notice that someone filed bug
>54667, requesting such a feature, and that has been deferred to post 3.0.
>I wasn't able to find any explanation of why it was removed, and I was
>hoping that someone could clue me in.
Yes, it has been removed. The reason is that users were expecting more
from this option than what it was supposed to do. Three different
users were expecting three different behaviors from the same option.
This means this option was not properly done and we removed it.

54667 is not the same request. 54667 asks for an option to preserve
existing line splitting. This means that the code formatter should not
change the way the line is divided.
Right now there is no plan to support this before 3.0 due to lack of
time. It might be reconsidered post 3.0.
--
Olivier

Re: Code formatter in M8: Preserve exisiting line breaks? [message #154898 is a reply to message #154895]

Mon, 19 April 2004 09:54

Eclipse User

Olivier Thomann wrote:

> Yes, it has been removed. The reason is that users were expecting more
> from this option than what it was supposed to do. Three different
> users were expecting three different behaviors from the same option.
> This means this option was not properly done and we removed it.

Hi Olivier,

I can't help but wonder if I was expectation number four. ;)

Thanks very much for the explanation.

Cheers,
Dave

Previous Topic:	Editor Could not be initialized
Next Topic:	Extending incremental java builder

Goto Forum:

-=] Back to Top [=-

Current Time: Thu Apr 24 23:33:38 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter