Community
Participate
Working Groups
3.1 RC2 This happens with or without the fix for bug 52921. Examples see there.
This seems to fail for the same kind of reason as bug 52921. If the code contains a space after the '*', a new space gets added.
It not only shifts everything one space to the right, it also adds an empty line before and after the text which is even more anoying. It seems that <pre> whatever </pre> stays okay while <pre> whatever whatever </pre> starts moving...
Please read comment 0 and bug 52921 mentioned there.
I just checked I20050617-1618 and inserting new lines is gone but non-Java-code is still shifted to the right with every format operation. Switching off "Format Java code snippets" will help. BTW, at the beginning, I didn't notice that "Format Java code snippets" will affect <pre> elements so it might be a good idea to make this explicit in the text, i.e. "Format Java code snippets inside <pre> tags"
*** Bug 96268 has been marked as a duplicate of this bug. ***
The spacing problem remaining as of comment 4 still happens with: Version: 3.1.0 Build id: I20050627-1435 Besides the snippets mentioned in earlier comments, the following text also triggers the problem: <pre> <test> </pre> Formatting this snippet repeatedly adds a space in front of < with each iteration. Going by comment 2 (which is entirely correct), one might infer that <pre> elements with only one line of content do not trigger the bug but as the case above illustrates, it is not the case for *all* one-line <pre> elements. Like in previous cases, turning off "Format Java code snippets" also prevents the bug to show up with the snippet above.
>The spacing problem remaining as of comment 4 still happens with: Please take a look at https://bugs.eclipse.org/bugs/page.cgi?id=fields.html#status
*** Bug 106262 has been marked as a duplicate of this bug. ***
*** Bug 110787 has been marked as a duplicate of this bug. ***
Ownership changed.
*** Bug 114257 has been marked as a duplicate of this bug. ***
*** Bug 113545 has been marked as a duplicate of this bug. ***
*** Bug 116437 has been marked as a duplicate of this bug. ***
*** Bug 116443 has been marked as a duplicate of this bug. ***
*** Bug 118140 has been marked as a duplicate of this bug. ***
*** Bug 119439 has been marked as a duplicate of this bug. ***
*** Bug 130724 has been marked as a duplicate of this bug. ***
*** Bug 147291 has been marked as a duplicate of this bug. ***
*** Bug 151457 has been marked as a duplicate of this bug. ***
*** Bug 153419 has been marked as a duplicate of this bug. ***
*** Bug 154027 has been marked as a duplicate of this bug. ***
*** Bug 157540 has been marked as a duplicate of this bug. ***
Well, so what happens with this bug? It has been detected in 3.1 and still can be found in 3.2. Is there any plan to fix it in 3.3? Please keep in mind, that documentation is very important and shall not be inhibited by tedious bugs like this.
Yes, this is intended to be fixed for 3.3. Right now I have to focus on other things. But if you want to provide a patch, I'll review it.
*** Bug 161184 has been marked as a duplicate of this bug. ***
*** Bug 164259 has been marked as a duplicate of this bug. ***
Olivier, is there any chance we can fix this for 3.2.2? From the number of dups, it seems like it's really causing grief for people.
I can investigate a fix. A solution for 3.2.2 will depend on the risk involved with the fix. I cannot make any promise for 3.2.2 for now.
Risk? This bug means that no one can put code examples in their JavaDoc! Certainly in our project we're endeavouring to do that as we have many users who are new to the GUI toolkit we present and so need to embed all kinds of code snippets. At the moment, every time you hit code format, everything precesses to the right one character, and your version control tool thinks you've got a change on those lines. Endlessly removing single space characters manually is getting really really old. Is there any shred of hope you can offer us? AfC Maintainer java-gnome.sourceforge.net
*** Bug 169330 has been marked as a duplicate of this bug. ***
(In reply to comment #29) > Risk? This bug means that no one can put code examples in their JavaDoc! I know. I'll investigate a fix.
Any volunteer to try a patch?
Created attachment 56462 [details] Proposed fix This patch seems to work fine for test cases issued from this bug and its duplicates.
Created attachment 56463 [details] Regression tests
Released for 3.3 M5 in HEAD stream Released for 3.2.2 in R3_2_maintenance stream
You can pick up the update on: http://www.eclipse.org/jdt/core/r3.2/index.php#UPDATES and replace the jdt.core plugin in the latest 3.2 maintenance stream. Let me know asap if you find any problem.
+1 for 3.2.2.
I just tested it, and it appears to work perfectly now. AfC
The behavior of build M20070112-1200 on the test case of comment #6 is not perfect, but it is different from the one which triggered this bug. I opened the fup bug 170580 to track that separate issue. The original defect is fixed. Verified for 3.2.2 using build M20070112-1200.
*** Bug 171485 has been marked as a duplicate of this bug. ***
Verified for 3.3 M5 using build I20070205-0009
*** Bug 178432 has been marked as a duplicate of this bug. ***
*** Bug 194533 has been marked as a duplicate of this bug. ***
