-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
:reload
should fail if unsaved changes
#5680
Comments
I think your request relates to: #4734 |
This would be doubly useful with I end up using
|
I meant it is in the same genre of feature, preventing unwanted data loss. I was probably being too general and not much help, soz! |
Np! Cross-referencing is great. |
Ill try to do this |
I opened a pr for this |
@Pablu23 Can you mention this Issue # in your PR (as |
Ahh yes I just did it, this is my first time contributing so I didnt know that. Thanks :) |
hmm, I think this may be related to something that bit me today where I put something up for PR, committed some suggestions from the GitHub UI, and then pulled so that I could address other issues but Helix didn't reload the file/buffer with the local changes so I ended up losing some work |
I'd like to suggest the
reload
command to fail if there are unsaved changes and adding an explicitreload!
that discards unsaved changes, similar toq
orbc
.Currently,
reload
discards changes anyway.Sometimes it's useful to reload a file only if there aren't any changes. For example, when changing the underlying file through another source I reload to not revert the changes on the next save in helix. However, if I have unsaved changes, I'd like that helix prevents me from reloading so I don't lose the changes. I know I can undo, but sometimes the changes are not visible in the current window. An explicit confirmation would be better.
The text was updated successfully, but these errors were encountered: