Bug 303266 - enhance eclipse compare to honore column limitation
Summary: enhance eclipse compare to honore column limitation
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Compare (show other bugs)
Version: 4.0   Edit
Hardware: PC Windows XP
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Compare-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-18 21:17 EST by frankar CLA
Modified: 2019-09-06 15:31 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description frankar CLA 2010-02-18 21:17:18 EST 
Build Identifier: 

RDz uses Eclipse Compare infrastructure for all Compares - Host file or Local - and Eclipse compare editors know nothing about columns - so its not possible to introduce a column specific or column restricted compare in the current infrastructure .
A customer is requesting this function

Reproducible: Always
Comment 1 Pawel Pogorzelski CLA 2010-02-19 04:51:32 EST 
Please specify more detailed steps/description as the limitation is not clear.
Comment 2 Pawel Pogorzelski CLA 2010-02-19 04:52:33 EST 
And please set the Version field appropriately.
Comment 3 frankar CLA 2010-03-15 14:55:47 EDT 
In the preferences - LPEX - compare - select column restricted comparison 
this preference is not being honored in the eclipse comparison  

If you start up a compare with local history  and you had a change in column 73 
eventhough you have restricted comparison selected the line will be marked as difference.
Comment 4 Eclipse Webmaster CLA 2019-09-06 15:31:20 EDT 
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.

If you have further information on the current state of the bug, please add it. 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.