-
Notifications
You must be signed in to change notification settings - Fork 23
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
Emacs 26 xref
window management broke code1
#127
Comments
xref
broke code1xref
window management broke code1
Couldn't reproduce it locally with, but did encounter some weirdness when using code1 while Your repro steps don't mention if |
I have purpose-mode enabled. |
I was able to reproduce this with |
I think I found the bug, will fix tomorrow or the day after. |
Should be fixed by a393b85 |
This fix made things much worst. Now a dired buffer will pop open and take over the edit buffer whenever I visit a file. The post-command-hook that updates the dired buffer also put it onto the edit buffer after every command |
Reverted for now. |
Actually my mistake, the buffer does display at the correct window with this fix and the xref problem is gone, but hide-details mode did not take effect because that mode is buffer-local you have to wrap it in a with-current-buffer. I'll submit a fix now. |
…cs 26, this fix lets purpose handle displaying it
Ah, ok. Merged the fix, thanks. |
Steps to reproduce
(purpose-x-code1-setup)
in.emacs
(xref-find-definitions)
(I visitedcompany.el
)company-backends
)M-.
xref
buffer is covered with an extradired
bufferq
exits the dired bufferq
again to exit thexref
bufferdired
buffer we just quit and buried.q
twice to exit the dired bufferExpected behavior
The extra dired window should never show up to begin with.
I've git-bisected this issue to be caused by this commit to Emacs 26, all subsequent commits shows the same behavior.
I'm not exactly sure what's going on here, does this have something to do with some weird interaction with #98 ?
P.S. I have
pop-up-frames
set tonil
.The text was updated successfully, but these errors were encountered: