Add option to jump to modified buffers without confirmation #287
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
This commit adds the option to jump directly to a buffer without being prompted for confirmation. If the `dumb-jump-confirm-jump-to-modified-file` variable is nil, then jumping to a modified buffer will print a warning message but will not wait for confirmation
|
Thanks for opening this! I'll take a look after work today. |
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.
Thanks for the dumb-jump—it's a great package and the simplicity really appeals to me. This is a PR for a patch that I find personally useful and thought others might as well.
It adds the option to jump directly to a buffer without being prompted for confirmation, even if that buffer is modified. I find that this is more often what I want, especially when jumping back up to the definition of a function defined earlier in the file (which, if I have been editing lower in the file, won't have moved at all).
Specifically, if the
dumb-jump-confirm-jump-to-modified-filevariable is nil, then jumping to a modified buffer will print a warning message but will not wait for confirmation.I also revised the README to explain this additional option.