Bug 395587 - indentation changes not correctly detected
Summary: indentation changes not correctly detected
Status: REOPENED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 4.2.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2012-12-03 05:38 EST by Marvin Fröhlich CLA
Modified: 2020-05-12 02:09 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marvin Fröhlich CLA 2012-12-03 05:38:46 EST
When I use the compare view to compare two revisions of the same class and one change is, that I enclosed some lines in a new block and hence increased the indentation, then the comparator goes mad.

It is impossible to describe, what the compare looks like in this situation. But you can easily reproduce it with the above steps.

I guess, this happens because eclipse doesn't expect line-wise marking, but char-wise, which is a different story.

I would expect the compare view to only mark the changed indentation to highlight as changes. This could for example be the beginning of the lines.
Comment 1 Dani Megert CLA 2012-12-03 06:49:28 EST
This comes from text compare.
Comment 2 Marvin Fröhlich CLA 2016-03-15 09:50:51 EDT
Is text compare a separate project? Isn't it part of the eclipse project? Will this bug be addressed?
Comment 3 Dani Megert CLA 2016-03-15 11:44:58 EDT
(In reply to Marvin  Fröhlich from comment #2)
> Is text compare a separate project? Isn't it part of the eclipse project?
> Will this bug be addressed?

Help is welcome.
Comment 4 Eclipse Genie CLA 2020-02-10 13:12:24 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. 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.
Comment 5 Marvin Fröhlich CLA 2020-04-07 01:36:35 EDT
This bug still exists. Just reopening to make sure, it doesn't go under.
Comment 6 Lars Vogel CLA 2020-05-11 15:54:38 EDT
Please reopen if the problem still persists.
Comment 7 Marvin Fröhlich CLA 2020-05-12 02:09:34 EDT
Yes, it still persists.