Community
Participate
Working Groups
Using the compare editor is difficult when you are comparing content that has long lines of text. Because the normal Orion text editor supports word-wrap, it is easy to build lines like this (e.g. MD files where you use "one line per paragraph"). It would be useful to have this feature on the compare editor too, so that, for example, you could more easily check what has been changed before committing changes to the repo.
Created attachment 256803 [details] work in progress
Created attachment 261195 [details] github-compare-with-word-wrap.png The github compare viewer always uses word wrap. I am reviewing and making changes to the ARIA 1.1 spec, which is mostly HTML, and there are many long lines. I cannot reasonably use the Orion compare viewer to see my changes because not only do I need to scroll... but I need to scroll both sides of the compare viewer to the exact horizontal position in a very long line of text, and then I need to do that for every change, because each change is at a different horizontal scroll point than the change before it. The "unified diff" compare viewer does not help much - it does cut the amount of scrolling down, but it still takes too long to find the exact horizontal position. I end up dropping down into github every time I need to do a compare. I have attached a screen snap of the github changes viewer. It is quite nice.
Created attachment 261196 [details] orion-compare-viewer.png For comparison, here is a screen snap of the Orion compare viewer on the same change(s). You can't see the actual change because it is scrolled horizontally to the right. (The collapsed lines feature is also really nice, because note that you can see multiple changes at once in the github compare viewer, and you can only see the first part of the first changed line in the Orion compare viewer).
Changing from "enhancement" to "normal" (i.e. "bug") because when comparing javascript or css files, word wrap is an enhancement... but for comparing html files it's an absolute necessity.
*** Bug 489578 has been marked as a duplicate of this bug. ***
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04002.html
Reopening, as I am currently comparing changes in a bunch of html files, and it is quite annoying and painful to have to scroll both files to see the changes that are cut off on the right hand side of both the new and old file.
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg04114.html
Would be nice to have this feature on board.
Reopening: triaged.
It is not only the "compare" process which is obstructed by the lack of automatic line wrapping, but also the conflict merging that is hampered. Just today a coworker of mine asked me to insert manual line breaks in our Asciidoc documentation as a workaround in order to be able to reasonably resolve merge conflicts in Eclipse without resorting to fully manual merging. This clearly is a waste of time as a result of this editor's limitation. See Notepad++ compare plugin in contrast, were line wrapping can be enabled.
