Regarding moved/deleted files, I think we should let it fail. Reasons:

- That's how apps usually works (well at least the few ones I just checked)
- The file might be on an drive that is currently (but not permanently) unmounted
- It might still be useful to see that you have recently worked with a file even if it has since been deleted

The second of these reasons is the most compelling to me.

Corruption might be more worrisome, but I'm not sure how to detect it. Almost any filename is legal under Unix systems, and path length can go up to 4,096 chars under Linux. Maybe we should at least impose some OS dependent length limit. That would at least get rid of *huge* strings of corrupted garbage.

Or is there something in the Java language libraries that can check for filename validity? `new java.io.File(fileName)` seems to accept just about anything except `null`.

In any case, maybe there should be a distinction between the displayed path and the stored path. Some legal paths are nevertheless too long to be fully shown in the menu, and I hadn't thought about that.