Skip to content
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

Having a more informative VC status in ibuffer-vc #23

Open
makp opened this issue Jun 23, 2018 · 1 comment
Open

Having a more informative VC status in ibuffer-vc #23

makp opened this issue Jun 23, 2018 · 1 comment

Comments

@makp
Copy link

makp commented Jun 23, 2018

My impression is that, because ibuffer-vc relies on vc-state to get the status of a file, the column "VC status" in the ibuffer-vc cannot differentiate between the following two situations: (1) a file was modified and the changes were not committed; and (2) the changes were committed. That is, the VC status for both situations is "edited". As suggested by someone here, the function vc-refresh-rate can be used to fix this situation. Still, after using vc-refresh-rate, the VC status does not distinguish whether you pushed the commit or not to the remote repository (in both situations the VC status is "up-to-date"). Is there any way of distinguishing these different states with the "VC status" column in the ibuffer-vc?

Thanks for writing ibuffer-vc. It's an extremely useful package!

@manuel-uberti
Copy link

This would be an interesting add for sure.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants