-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
Version Control Actions #6101
Comments
I was planning to go in a different direction and implement all vcs features in term of generic commands.
|
In terms of an idea for the UI for blame. Similar to the presentation you get in github on the web, the vim plugin Though the thing that I find the most powerful in blame mode are the additional actions you have from that mode:
I've found this ability to interact with the history of a file amazing to help understand why code ended up the way that it is. It is also the sort of action that is fantastically easier to do in an editor than it is to do with a tool in the cli next to your editor. |
In the same spirit as
<space>-a
(perform code action
) it would be a nice addition to have something similar for version control.There already is support for highlighting code changes, but then also having for example
<space>-v
forperform version action
(just picked some unused char) to get a list of possible version control actions for a line (eg. stage/unstage, discard etc.) would be a great addition IMO (which quite naturally can be made generic to work with different VCS). Obviously the exposed functionality can start small and grow. This would require some pondering regardingreload
and how that should be handled (maybe just a warning that reload will be performed, or a secondThis will reload current buffer, continue? [Y/n]:
confirmation could be enough).I tried looking through the docs and issues, but didn't find it being mentioned (possible I didn't look hard enough).
The text was updated successfully, but these errors were encountered: