Pass 'visible to get-buffer-window #235
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
If I have two frames, with the *compilation* buffer in one frame and use next-error in the other frame, I get this error: Wrong type argument: window-live-p, nil This happens because get-buffer-window returns nil. The fix is to pass 'visible to get-buffer-window, which will pick any visible frame from the same terminal.
|
This one is pretty trivial and I've been using it for a while, so I'm just going to merge it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If I have two frames, with the compilation buffer in one frame and
use next-error in the other frame, I get this error:
Wrong type argument: window-live-p, nil
This happens because get-buffer-window returns nil. The fix is to
pass 'visible to get-buffer-window, which will pick any visible frame
from the same terminal.