2 
emacs: 26.2
spacemacs: develop (19c429e)
magit: 20190609.1424

Some time ago (e.g. 20190222.1746), magit's window management used to be different from how it currently is. For example, magit-status would always try to use an existing window, or if there was only one window in the frame, it would open a split (as if split-window-right was called). Now, magit will always open a new window.

Another example is that previous-buffer will skip over magit buffers, whereas before it would land on magit buffers.

I've been looking through the commits and so far I haven't seen any with an obvious commit message that signals these changes. Is this behavior the new default behavior? Is there any way to customize that it work like it used to?

Improve this question
2
  • I have not made a change to Magit that would explain this behavior. Maybe you are using a starter-kit that made those changes? Packages exist that try to take over window management. Maybe you have recently installed one of those? Also see magit-display-buffer-function.
    – tarsius
    Jun 14, 2019 at 8:53
  • @tarsius thanks for your response. magit-display-buffer-function is magit-display-buffer-traditional. So I have two machines: laptop was on magit 20190222.1746 and desktop is on 20190609.1424`. Both have the same version of emacs and spacemacs (although the laptop's packages are a bit out of date), so I assumed that the different versions of magit must have been the culprit. So I updated magit on the laptop, and it's not. So it could be any of 123 out-of-date packages that is causing this. Bleck. Can't think of any way to figure out which one other than updating one at a time
    – KevinOrr
    Jun 14, 2019 at 16:26

1 Answer 1

Reset to default
0

As the comments on the question indicate this seems to be caused by an undetermined third-party package.

Improve this answer
3
  • Can you add what resolved the issue (updating packages in this case)?
    – user12563
    Jun 17, 2019 at 15:58
  • I don't even know whether @KevinOrr was able to resolve the issue, so no. (By adding an "answer" I am mostly signaling that I am done here, unless more relevant information is provided.)
    – tarsius
    Jun 17, 2019 at 18:48
  • Yeah that's fair. It's going to take me a while to debug, but it's most likely not a magit issue
    – KevinOrr
    Jun 17, 2019 at 19:26

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.