Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!spool.mu.edu!uwm.edu!rpi!dali.cs.montana.edu!masscomp!peora!tarpit!osceola.cs.ucf.edu!eww
From: eww@engr.ucf.edu (Mr. Eric W. Wampner)
Newsgroups: comp.sys.amiga.advocacy
Subject: Re: How other GUIs handle deletion.
Message-ID: <1991Feb4.210749.146@osceola.cs.ucf.edu>
Date: 4 Feb 91 21:07:49 GMT
References: <1991Feb2.160133.24350@news.iastate.edu>
Sender: news@osceola.cs.ucf.edu (Network News)
Organization: engineering, University of Central Florida, Orlando
Lines: 24

In article <1991Feb2.160133.24350@news.iastate.edu> geff@iastate.edu (Underwood Geoffrey Dale) writes:
>Amiga --
>	I don't know how the Amiga trashcan works.  Would somebody mind
>posting an explanation?
>
<stuff deleted>
Pretend this a C switch, and I forgot to use break.
Substitute "Cute Black Hole which swirls," for "Ugly Standard Trashcan"
Substitute ~/NeXT/.NeXTtrash for dev:Trashcan, only one user!

>
>NeXT --
>	When a file icon is placed in the Black Hole (or Recycler in 2.0), the
>Workspace moves the file to ~/.NeXT/.NeXTtrash.  For those readers unfamiliar
>with UNIX conventions, "~" is the current user's home directory -- one user,
>one Black Hole.
>	Since files are placed in a special directory, it is easy to find out
>whether or not files are in the Black Hole.  Because of this, almost-deleted
>files are kept until explicitly purged.

<point of conversation deleted :>

Eric Wampner
eww@heretic.engr.ucf.edu