No subject

clear, important and appropriate to this discussion.

Based on the work that I did in making the ISO_9660 compatible file
system, I envision that a change to the file name scanner to include
the "/" character in a file name would allow the command in the
example to execute, and to give the results described, on a "flat"
file system.  Moreover, it would give additional power.

I have some objections to this solution.  You may also object to this
solution.

Can you explain why?


From: "Ghost in the Machine" <cangelich at famvid.com>
| > Let me explore the following user interface scenario.
| >
| > 1.  A command of the nature
| >         System.Directories eMail/Y02/July/*
| > produces list of file names that the user named and saved from email
| > received in July 2002.
| >
| > Is this the sort of thing you are missing?
| 
| Don't be patronizing.
| 
| I want to be able to separate sets of files into subdirectories
| not clump them all together in one huge directory.  MSDOS
| v2.1 had subdirectories - did  you notice that?
| 
|