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

"File not found" infobar still present after reloading file #1373

Closed
mihoe opened this issue Jan 20, 2017 · 1 comment
Closed

"File not found" infobar still present after reloading file #1373

mihoe opened this issue Jan 20, 2017 · 1 comment

Comments

@mihoe
Copy link

mihoe commented Jan 20, 2017

I often see a "File ... was not found on disk!" infobar when a file becomes unavailable while being edited in Geany. When the file reappears (e.g. after re-mounting a disk or network share or when undoing a rename or delete operation outside of Geany) and I reload the file (by pressing Ctrl+R or via the File menu), the tab title turns from red to black, suggesting that the reload was successful. However the "File not found" infobar remains visible, and I have to click the Cancel button to make it disappear.

The "File not found" infobar should behave like its sister infobar for a timestamp mismatch, "The file ... on the disk is more recent than the current buffer", which disappears automatically after reloading the file.

Even better, Geany could be a little more patient and/or intelligent when a file becomes unavailable on disk. Most of the time I see this error message after resuming my machine from suspend, when a network share on which a file that I'm editing in Geany resides needs a couple of seconds to come up again.

Ideally Geany could (a) use a slightly longer timeout before throwing an error, at least while no actual editing is being done or the user doesn't try to save the file and/or (b) retry to locate the missing file a couple of times, with short intervals in between, before showing an error (or hiding the infobar automatically when the file reappears on disk).

@mihoe
Copy link
Author

mihoe commented Jan 20, 2017

Right after submitting this I've stumbled over #1330, which seems to describe the exact same problem and has very similar suggestions. Sorry, my bad!

@mihoe mihoe closed this as completed Jan 20, 2017
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

1 participant