Allow killing indirect when base buffer has already been killed.#240
Open
tmurph wants to merge 1 commit intoemacsorphanage:masterfrom
Open
Allow killing indirect when base buffer has already been killed.#240tmurph wants to merge 1 commit intoemacsorphanage:masterfrom
tmurph wants to merge 1 commit intoemacsorphanage:masterfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
An unrelated activity killed a base buffer in a way that left its indirect buffer hanging around, and when I tried to kill off the indirect buffer manually I was blocked by an error in this hook function. (
with-current-buffercomplains when trying to activate a killed buffer)So here's a quick patch to guard against that issue.