Community
Participate
Working Groups
In the Apply Patch wizard show which context lines has been applied with a fuzz factor. An idea is to add and color "diff lines" for such context lines. I would use a low distractive color like yellow.
Created attachment 91185 [details] Mockup Mockup showing how this could look like. Yellow regions are the ones applied using the fuzz factor. Gray regions are not part of the hunk. I'm wondering if thers is a situation when used fuzz factor is greater then 1 but only one line of context doesn't match shouldn't we indicate it somehow? In other words, shouldn't we show that actually more then 1 line have been ignored? Shoudn't they be part of a "yellow region" too? If yes, in the attached mockup, line [8] would also be marked yellow, even though it perfectly matches with the content of the patch (hunk).
I'm afraid I won't make it in 3.4 M7, which is in fact the last iteration for 3.4. Thus I'm moving it to 3.5.
We haven't investigated the issue during 3.5 and we don't plan to address it now. I'm removing the target milestone but we'll set more realistic one when we have feedback from anyone interested in fixing this.
Taken from bug 217076, comment 2: > (...) it would be good to show a warning in cases where none of the context lines is > actually used when the patch is applied.
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.
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.
