You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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!
The text was updated successfully, but these errors were encountered:
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 functionvc-refresh-rate
can be used to fix this situation. Still, after usingvc-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!
The text was updated successfully, but these errors were encountered: