emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why @#! is not Emacs using the Recycle bin on w32?


From: Lennart Borgman (gmail)
Subject: Re: Why @#! is not Emacs using the Recycle bin on w32?
Date: Fri, 29 Aug 2008 01:48:58 +0200
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666

David De La Harpe Golden wrote:
> Lennart Borgman (gmail) wrote:
>> I just deleted a file because I misunderstood dired. I needed that file
>> (of course).
>>
>> And then I found that dired did not make any backup and did not use
>> windows Recycle bin.
>>
>> This behaviour does not make me trust for example GNU/Linux. I would
>> beleive this is a behaviour implemented after how things work there. Is
>> this correct? Does Emacs behave this way on GNU/Linus too?
> 
> Traditionally on unix and gnu+linux, when you say you want a file gone,
> the system and programs believe you.  This is quite widely regarded as a
> feature. And personally, I think trashcans just suck, they're a terrible
> UI metaphor, 

Thanks, I would be glad for no lessons. Why do you think they suck? I
think it is a very good metaphor, easy to understand.

> apart from the security risks.

This is a much lesser risk than loosing your files. If you are handling
sensitive materials on a computer and do not know what you are doing
then ... ;-)

> Things like
> versioned/snapshotted filesystems with timeline views are so much neater.

Ok, I see. But if that not is used then trash cans are very good.

> That said, on typical gnu+linux desktops, there IS a trash can provided,
> but emacs dired delete AFAIK doesn't use it.  It probably could (or
> another "move to trash" command be provided) with relatively little
> effort (nonetheless I'm not volunteering...), the spec is very simple
> and widely adopted.
> http://www.freedesktop.org/wiki/Specifications/trash-spec

Thanks. I am sure it is easily equal on w32. Actually I think someone
proposed it a while ago. I really thought it was implemented.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]