Re: Is this a buglet.. nndrafts:draft renegades

["Matt Armstrong" <matt+dated+1007571874.3d8167@lickey.com>]

Harry Putnam <reader@newsguy.com> writes:

> "Matt Armstrong" <matt+dated+1007413841.964140@lickey.com> writes:
>
> [...]
>
>> Actually, I reverse my opinion.  C-x k deletes a buffer, not a file.
>>
>> I have C-x C-s C-x k deeply ingrained in my muscle memory -- it is the
>> "save to disk, then delete buffer" key sequence.  Data does not get
>> lost when doing this.
>
> In the sense that a composition is a file, C-x k does kill the file
> and data is lost in every other usage.  However it does prompt for
> the permission.

I think we agree.  C-x k does not delete the file from disk if it has
been explicitly saved -- it does get rid of any autosave file and that
is fine with me.

It works this way in the drafts folder too (perhaps only with recent
CVS though).


> The sequence below assumes `file' does not yet exist.  Just like a
> fresh composition buffer.
> C-x C-f file 
> type Start
> C-x k  prompt: yes 
> The file is removed and data is lost.   Why should a composition
> buffer be any different?

I agree that it shouldn't be different.


>> If C-x k suddenly deletes the message out of the drafts folder, I'll
>> end up accidentally deleting drafts left and right.
>
> Why is this so perilous compared to behavior on a not existent file
> in C-x C-f file?

I'm saying that after I save the message (C-x C-s), C-x k should not
delete it from drafts.  But I don't think you want that either.


-- 
matt