... ping ...
On Mon, Jan 21, 2019 at 01:47:37PM +0100, Pavel Sanda wrote:
> On Fri, Jan 18, 2019 at 09:10:13PM -0500, Richard Kimberly Heck wrote:
> > On 1/18/19 8:29 PM, Pavel Sanda wrote:
> > > I guess my point now is that experienced user is not expecting
> > > emergency file to be renamed an
On Fri, Jan 18, 2019 at 09:10:13PM -0500, Richard Kimberly Heck wrote:
> On 1/18/19 8:29 PM, Pavel Sanda wrote:
> > I guess my point now is that experienced user is not expecting
> > emergency file to be renamed and stored, so some hint should be provided.
>
> How about a dialog after that's done
Am Freitag, 18. Januar 2019 04:57:19 CET schrieb Richard Kimberly Heck
:
> commit b804e8851c33b68caa5057e809a12333741dfe2e
Typo:
> + "You should do so manually.
> Otherwise, you will be"
> + "asked about it again the ne
On 1/18/19 8:29 PM, Pavel Sanda wrote:
> I guess my point now is that experienced user is not expecting
> emergency file to be renamed and stored, so some hint should be provided.
How about a dialog after that's done: "Emergency file saved as
whatever.lyx"?
>>> What I would find as a real impro
On Fri, Jan 18, 2019 at 04:42:29PM -0500, Richard Kimberly Heck wrote:
> > The previous code
> > forced you to do *something* about the situation when it's most due --
> > until you deal with the emergency file properly, you will be asked.
> Not really. You can perfectly well leave the file sittin
On 1/18/19 7:36 AM, Pavel Sanda wrote:
> On Fri, Jan 18, 2019 at 04:57:19AM +0100, Richard Kimberly Heck wrote:
>> commit b804e8851c33b68caa5057e809a12333741dfe2e
>> Author: Richard Kimberly Heck
>> Date: Wed Jan 16 11:13:53 2019 -0500
>>
>> Rename emergency file when it is kept.
>>
>>
On Fri, Jan 18, 2019 at 04:57:19AM +0100, Richard Kimberly Heck wrote:
> commit b804e8851c33b68caa5057e809a12333741dfe2e
> Author: Richard Kimberly Heck
> Date: Wed Jan 16 11:13:53 2019 -0500
>
> Rename emergency file when it is kept.
>
> Otherwise, we will ask about it again next
