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

Use Magit 2.8's built-in fullscreen status display function #7085

Closed
wants to merge 1 commit into from

Conversation

houli
Copy link
Contributor

@houli houli commented Sep 11, 2016

Magit 2.8(changelog here https://emacsair.me/2016/08/21/magit-2.8/) added it's own set of display functions one of which is a fullscreen display function that acts the same way as Spacemacs' version. These are documented here https://magit.vc/manual/magit/Switching-Buffers.html. This removes the need for Spacemacs to maintain its own version of a fullscreen status function.

@@ -358,7 +358,7 @@ Press [_b_] again to blame further in the history, [_q_] to go up or quit."
'spacemacs/magit-toggle-whitespace)
;; full screen magit-status
(when git-magit-status-fullscreen
(setq magit-display-buffer-function 'spacemacs//fullscreen-magit)))))
(setq magit-display-buffer-function 'magit-display-buffer-fullframe-status-v1)))))
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe we can do away with the layer variable altogether and just document this one instead?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes that's possible. Also those documentation sections in the README could also be cleaned up a bit as well to use the layer variable system rather than defining them in user-init

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any thoughts about how to proceed with this PR?

@TheBB
Copy link
Collaborator

TheBB commented Oct 17, 2016

Thanks! Cherry-picked in develop. Let's keep it like this for now. You can safely delete your branch.

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

Successfully merging this pull request may close these issues.

None yet

2 participants