Bug 465511 - Next/previous difference in Synchronize view makes you jump to the next/previous file instead
Summary: Next/previous difference in Synchronize view makes you jump to the next/previ...
Status: CLOSED DUPLICATE of bug 361306
Alias: None
Product: EGit
Classification: Technology
Component: UI (show other bugs)
Version: 3.4.2   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-26 17:48 EDT by Mauro Molinari CLA
Modified: 2015-04-29 18:04 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mauro Molinari CLA 2015-04-26 17:48:47 EDT
The next/previous difference buttons in the Synchronize view causes the UI to jump to the next/previous changed file, instead of to the next/previous difference in the currently compared file.

In Subversive, for instance (and I would say in CVS, too, but I can't bet on this since a long time has passed), these buttons behave as follows:
- if there's no open compare editor, they open a new one on the next/previous file and select the first/last difference in it
- hitting again causes the next/previous difference to be selected within the currently compared file
- when you reach the end/start of file, another press causes the first/last difference of the next/previous file to be shown and selected (the previous compare editor is closed, a new one is opened)

This is very comfortable to use and rational. With eGit, these buttons are almost useless. I must use the next/previous difference within the compare editor, but they are limited to the scope of the currently open editor. In fact, in Subversive, for instance, when you reach the last difference and you click again the "next difference" button in the compare editor, you're asked if you want to go to the beginning of the current file or to the beginning of the next changed file. In eGit, only the first option is proposed.

So, there's no way to iterate over all the differences without having to manually jump from one file to the other whenever you reach the end of a changed file.
Comment 1 Mauro Molinari CLA 2015-04-29 18:04:11 EDT

*** This bug has been marked as a duplicate of bug 361306 ***