[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 54810] kword destroys data when space to write is empty
From:       Nicolas Goutte <nicolasg () snafu ! de>
Date:       2004-03-16 18:23:26
Message-ID: 20040316182326.6166.qmail () ktown ! kde ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
      
http://bugs.kde.org/show_bug.cgi?id=54810      




------- Additional Comments From nicolasg snafu de  2004-03-16 19:23 -------
On Tuesday 16 March 2004 18:32, David Faure wrote:
> ------- You are receiving this mail because: -------
> You are the assignee for the bug, or are watching the assignee.
>
> http://bugs.kde.org/show_bug.cgi?id=54810
>
>
>
>
> ------- Additional Comments From faure kde org  2004-03-16 18:32 -------
>
> > I suppose that the problem is not really how to react
>
> Well it's good to agree on this first, before getting into coding mode :)
>
> > As for a retry, I do not know if it is useful, as a full partition
> > remains full (similar with over-quota.)
>
> I don't agree - if I wanted to save and my $HOME was full, I'd erase
> something and then click retry. A full partition doesn't remain full if you
> give the user time to clean up.

Well, I do not really care if it can be coded with a "Retry" (as long as there 
is a "cancel" too) and if this code can be ported back. (I had the feeling 
that it could not be easily done so.)

For me, "disk full" is an error like any other. We do not try to recover from 
the other errors. We just tell the user which error has occured. And it is up 
to the user to do something against it (and probably to call File/Save 
again.)

Have a nice day!
 ____________________________________
> koffice mailing list
> koffice mail kde org
> To unsubscribe please visit:
> https://mail.kde.org/mailman/listinfo/koffice
[prev in list] [next in list] [prev in thread] [next in thread]