-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Option to step through changes in revision history #5694
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
This is a great idea thanks for suggesting it @thumDer! It does feel like it's a bit of heavy lift for the UI to code this. Suggestion (if doing this all in one go is too much work), break this into two parts:
|
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
In GitHub and GitLab PRs, this is the review mode. Might depend on and more, or less, on |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
Still a good feature to add, but if you don't think it makes it on to the next year's roadmap perhaps you can throw it to a back burner queue @tommoor ? |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 5 days |
@hmacr what do you think, still remove stale flag? As a person who uses the diff UI often, I'd love to see this feature |
There was ongoing work in the recent past, we'll see if that can be taken forward. |
Discussed in #5693
Originally posted by thumDer August 16, 2023

It would be great to have a control on the revision views which allows the user to step through each and every changes that are part of the current revision. Currently the user has to go through the whole document and look for the highlighted parts, which is quite cumbersome on long documents. The way it is implemented in vs cvode is quite convinient:
The text was updated successfully, but these errors were encountered: