Suggestion: Move the text cursor to a more appropriate position upon viewing a backup

[unphased]

I notice that whenever I flip through backup versions the text cursor/caret always moves to the end of the file buffer.

1. If that revision of the file happens to not end with a newline, then the position is not at column 0 so it is difficult to read the timestamp (filename) since it shifts around a lot because the length of the last line changes. However even putting it at the beginning will not solve this issue completely (it will help it somewhat though) because the last line number may also change. So perhaps this can be addressed by printing a tab character at the beginning of the status line. I don't know if the status line handles tabs like that.

2. It would be convenient if the cursor is placed near the location of the changes which occurred in the file on that particular revision. It would consume time to have to scroll back to where you think the changes are, especially in a long file. This will likely require computing an incremental diff though. But that is also useful and can be made into a possible viewing format! see my other issue.

[joelpt]

Interesting ideas.

I have implemented a (mostly working) method of maintaining the approximately same buffer scroll position as you go back/forward in history, but I haven't addressed the actual cursor position yet.

The idea of jumping to the first or nearest change is interesting too. Perhaps a nice addon to that would be to jump to the change and automatically highlight (select) it, so you get an easy visual identification of the changed chunk (or chunks?). I'll think on it.

[unphased]

Wow that is a great idea, highlighting the changed areas. since the editor supports multi-highlighting, this might be even more appropriate than displaying an incremental diff! Though it would provide slightly less information, it is pretty elegant.