-
-
Notifications
You must be signed in to change notification settings - Fork 251
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
Expand on Status Sections #667
Conversation
for them on status buffer
now specific to pushremote and upstream. "unmerged_upstream", "unmerged_pushremote", "unpulled_upstream" and "unpulled_pushremote" are now available.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps we should document highlight groups for other plugin authors.
It is always so fun seeing how your project influences the rest of the ecosystem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yup! I have a WIP branch doing exactly that. #630
Splits unpulled/unmerged into two different sections for
@{upstream}
andpushRemote
.Top
nvim
, bottomemacs
.Also splits the internal repo's unmerged/unpulled to differentiate between pushRemote and upstream. This is useful if they are not the same, so you can get more detailed information about the current repo. If upstream and pushRemote are the same, then we'll only show the upstream sections on the status buffer.