Closed wyuenho closed 6 years ago
Couldn't reproduce it locally with, but did encounter some weirdness when using code1 while purpose-mode
is disabled (which I think is to be expected).
Your repro steps don't mention if purpose-mode
is enabled or not. Does this bug happen with or without purpsoe-mode
?
I have purpose-mode enabled.
I was able to reproduce this with open -a emacs --args -Q
and just window-purpose
and company
installed. I then M-x purpose-mode
and followed up with M-x company-mode
to warm up xref, and then tried M-.
on one of the backend symbols on company-backends
again.
I think I found the bug, will fix tomorrow or the day after.
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.
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
.