Community
Participate
Working Groups
The formatter in my project is supposed to leave lines at a length of 150 characters. However, in one file I do a long enumeration of all possible keywords. While the first few lines (about 50 lines, 476 keywords) are correctly formatted, the formatter gives up at one point without me seeing the reason, why. See the attachment for details.
Created attachment 222516 [details] A screenshot of the faulty wrapping behaviour Now the attachment...
There must be something about this file or your setting. I can't reproduce with a similar case. Have you customized the formatter, by any chance? If so, can you share the attached format and the file with the problem? It would be ideal if you can isolate the code that you have problem with and attach it here. Thanks!
Created attachment 222670 [details] File, formatted in a wrong way. Sorry about that. It seems to have something to do with comments, I inserted into the list. I tried it with different profiles and the problem occured in each one of them.
(In reply to comment #3) > Created attachment 222670 [details] > File, formatted in a wrong way. > > Sorry about that. > > It seems to have something to do with comments, I inserted into the list. I > tried it with different profiles and the problem occured in each one of them. Thanks and I can reproduce it with the file and as you said the comments seem to make the difference. And the happens regardless of the line wrapping width.
The formatter behaves very erratically when we have comments in an array initializer. Not sure if the fix can be simple. If anyone can work on this and come up with a patch, we can consider.
This should most probably get fixed with the patch in bug 303519
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. As such, we're closing this bug. If you have further information on the current state of the bug, please add it and reopen this bug. 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.