Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!rutgers!ames!ucbcad!ucbvax!COGSCI.BERKELEY.EDU!bryce
From: bryce@COGSCI.BERKELEY.EDU.UUCP
Newsgroups: comp.sys.amiga
Subject: Re: Workbench improvements
Message-ID: <8705010947.AA15600@cogsci.berkeley.edu>
Date: Fri, 1-May-87 05:47:10 EDT
Article-I.D.: cogsci.8705010947.AA15600
Posted: Fri May  1 05:47:10 1987
Date-Received: Sat, 2-May-87 14:10:54 EDT
Sender: daemon@ucbvax.BERKELEY.EDU
Lines: 27

In article <2967@well.UUCP> ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab) writes:
>
>	I always thought that the simplest and easiest-to-implement hack to
>the Workbench would be to create a file called "foo" (call it whatever you
>like; the name isn't important).  "foo" would be an ASCII text file that
>contains, on each line, the filenames of all the .info files in this
>directory.

It's called ".info" and appears in every directory that you open up from the
Workbench.  It consists of a date/time stamp and the ASCII text names of
all the .info files in that directory.  Sound about right?

type sys:.info opt h

When the date/time stamp does not match the modification date on the directory
the workbench reads EVERYTHING and updates ".info".  Face it, you where
out-hacked  :-) .

I am not sure if Workbench UPDATES this file or RE-WRITES it.  If no new
.info files appeared after after a scan it could just touch the date stamp
quickly.
Other things that Workbench may or may not already be doing:
RENAME instead of COPY if source and destination are on the same volume.
When 'snapshoting' a file SEEK() to the position bytes, do not re-write the
entire file.
   //
\\//  I liked the bouncy-ball logo better; but it's hard to do as text!