Limits of nano's automatic external file change detection

Limits of nano's automatic external file change detection

When a file opened in nano is modified by another process, the editor does not automatically update its internal buffer, leaving the user with a potentially stale view. The goal is to understand whether nano offers any mechanism to detect such external changes without discarding unsaved edits, and what constraints the current buffer‑based design imposes on implementing a reload or notification feature.

Does nano provide a built‑in command or option to check for modifications on disk and prompt the user to reload the buffer?

If no such feature exists, what are the recommended practices to avoid overwriting external changes when saving?

Are there any configuration flags, patches, or workflows that enable safe buffer refresh while preserving unsaved modifications?