As the original reported of 87101, I absolutely agree that the current solution is sub-optimal.
Since I suspect we can't modify all of the default applications to handle this situation sensibly (especially not in time for 8.04), the question then becomes, is it better to annoy users with the new behaviour, or to potentially lose their work with the old behaviour. I argued for the former because we have had users fall foul of their work being saved in a temporary location, but I hadn't considered the use case you've presented, so I think I should defer to the wisdom of others in picking a way forward. For what it's worth, one thing I've had in my mind all the time I've been thinking/discussing this bug, is the way gedit displays errors (although ironically it doesn't use this method in this situation): http://blogs.gnome.org/lucasr/files/2007/02/eog-error.png It just inserts an error message bar into the UI. The document could still be opened and be changed, but the user would undoubtedly notice the huge warning and could happily ignore it if they just want to play with some figures and not actually save things. I filed a bug against some common Ubuntu applications and their poor handling of read-only files - Bug #196488 -- attachments open in read only mode https://bugs.launchpad.net/bugs/209695 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
