GNOME Bugzilla – Bug 339171
delete inexistent files from recent menu
Last modified: 2007-01-14 17:40:44 UTC
some files may be in the recent menu, but no longer in the filesystem (i.e autodownloaded to /tmp from the browser and purged on boot). Since there's an error opening them, evince could remove them from the menu too.
Doesn't this bug belong to libegg / recent-files or shouldn't we update to recent file support landed in gtk to fix this problem?
in gedit we remove the doc from the recent list when it cannot be loaded. Not sure if the new recent stuff takes care of that autoamgically.
GtkRecent has property for that, so this bug should be easy to fix. But I think it's better to leave them. Sometimes files can't be accessible - you might forget the password or type something different. But it's not the reason to remove them from recent list. I'd better wontfix it. Probably Bryan will judge
well, at least in theory you could look at the kind of error you get and treat ENOENT in a way and permission problems in another way.
Sounds like special casing the permissions problems is a good way to work around this problem. I think removing non-existant files from the list would be a helpful thing. Assuming the permissions problem is handled such that those would stay around it'd be best to not have evince give an error message for a file _we_ offered them to open.
Right now, inexistent files are not shown in recent menu, but they are not explicitly removed from recent list, so that if they can be accessed in the future (i.e. because of permissions) they will be available.