Forward prev/next Diff keys to inline Diff from parent tab/window
It's very good that we have keyboard shortcuts Ctrl+N/M for prev/next Diff, but in the grander scope they are rendered sub-useful since these keys only work when one of the Diff panels has keyboard focus.
For example, in the Pending Changes view I like to review all changes before Checkin. To do this, I select the first item in the list. I can then use keys Up/Dn to walk around between changed items and the inline Diff is updated accordingly.
However, when there are many diffs in a file I want to review them all so I try the Ctrl+N/M shortcuts. That does not work without first mouse-clicking in one of the Diff panels. (Pressing Tab 4 times seems to work but that's kinda stupid...)
OK, then I want to move on to the next changed item, but that's not possible without first mouse-clicking in the list again. (Tab does not work at all here.)
This applies at least to the following views that have an inline diff:
* Pending Changes
* Diff Changeset
* "Explore changesets on this branch".
* 2D History (for a single file)
Please understand that for the "innermost loop" of reviewing changes it's very irritating to have to click with the mouse between every item when there are indeed keyboard shortcuts to do the required actions.
The simple solution to this would be to have the parent tab/window forward the Ctrl+N/M keys (and Ctrl+Shift+N/M) to the inline diff. Other keys need not be forwarded, for example the arrow keys work must differently depending on keyboard focus.
Duplicated, as explained on the entry :-)
WAIT!!! This is _not_ fully fixed in .806! It still won't work in Pending Changes, only in Diff Changeset etc. PLEASE fix Pending Changes as well, since that is one of the most important places to have this!
This has been fixed in 126.96.36.1996. Thanks!
Yes, sorry I missed that other uservoice. I'll move my comments there and you can decline this one.
Isn't this one a duplicate of http://plasticscm.uservoice.com/forums/15467-general/suggestions/10409298-restore-the-previous-next-item-keyboard-shortcut-i ??
Another way to solve my use case is to add specific keyboard shortcuts to the prev/next item buttons (and possibly the first/last item buttons as well).
It appears the key shortcuts mentioned in this blog post are no longer valid?