Fix refiling to current buffer (#644) #647
Merged
Conversation
This file contains 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
seflue
force-pushed
the
fix_refiling_to_current_buffer
branch
2 times, most recently
from
e6fcced to
89892f7
Compare
kristijanhusak
requested changes
Jan 8, 2024
I already did, see the force push. |
Fix edge case when refiling target is the current buffer, but content was captured.
seflue
force-pushed
the
fix_refiling_to_current_buffer
branch
from
89892f7 to
825fff6
Compare
|
Sorry, I forgot, that you don't do merge commits but squashing PRs onto master. I just did the requested rebase. |
SlayerOfTheBad
pushed a commit
to SlayerOfTheBad/orgmode
that referenced
this pull request
Aug 16, 2024
Fix edge case when refiling target is the current buffer, but content was captured. Co-authored-by: Sebastian Flügge <seflue@users.noreply.github.com>
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.
This fixes #644. @kristijanhusak Could you please merge #641 first, because this PR builds upon it. I will then rebase this one. If you decide to merge this directly, we can close #641.