Skip to content
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

No mechanism to detect/reload when a file changes on disk #7

Closed
rtzoeller opened this issue Nov 11, 2018 · 0 comments
Closed

No mechanism to detect/reload when a file changes on disk #7

rtzoeller opened this issue Nov 11, 2018 · 0 comments

Comments

@rtzoeller
Copy link

Currently if a file changes on disk while the file is loaded by gen3hex, there is no mechanism in place to detect that change. Having a way to (semi-)automatically reload a file from disk would let me use the editor in conjunction with other editing programs, and switch between them in a more seamless way.

In my mind there are two distinct scenarios for which the behavior might need to differ. The first is when the file is clean, and the version in memory matches the old version on disk, prior to it being modified externally. Visual Studio Code handles this by automatically loading the changes from disk, but allowing you to access the previous version through undo. Visual Studio prompts you to optionally reload it, and tells you that you have no unsaved changes in that editor.

The second scenario is when the file in memory is dirty, and unsaved changes exist. It appears the Visual Studio Code does not do anything in this case, while Visual Studio alerts you that the file has been changed in both places and prompts you to optionally reload it.

haven1433 added a commit that referenced this issue Dec 2, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants