Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!ukc!icdoc!sot-ecs!rhh88
From: rhh88@ecs.soton.ac.uk (Heywood RH)
Newsgroups: comp.sys.acorn,eunet.micro.acorn
Subject: Re: Continuing gripes about filename conventions...
Message-ID: <6733@ecs.soton.ac.uk>
Date: 12 Feb 91 13:26:59 GMT
References: <795@utrcu1.UUCP> <1991Feb11.100559.15181@and.cs.liv.ac.uk>
Sender: news@ecs.soton.ac.uk
Lines: 37

In <1991Feb11.100559.15181@and.cs.liv.ac.uk> rkl@and.cs.liv.ac.uk writes:


>have mixed case at all (I would still retain the *excellent* idea (ADFS has
>this too) of case-insensitivity when actually specifying filenames).

I agree. Thats one of the most friendly bits about adfs to me. Filenames
always look so much neater with a few capital letters thrown in but I
never do that on UNIX simply because its a pain in the *** to have to
type them in again. On the arc my files look readable and I can still be
bothered to type them in!! One nice feature in UNIX is the ability to
hit ESC when you're half way through typeing a filename in, and let unix
see if it can guess which file you mean!

>Enough slagging off for now. 10 characters for ADFS *is* far too small.
>I think somewhere around 30 or 40 would keep me happy - a new "V" (verbose !)
>format for RISC OS 3.00 perhaps ? :-)

Wouldn't half mess up the desktop filer window!! But thats someone elses
problem. I need super long filenames as well!!!

ttfn
RIK


     ______________________________________________________
    /                                                      \
   /                  Richard Heywood (Rik)                 \ 
  /                   rhh88@uk.ac.soton.ecs                  \
  \                                                          /
   \                   The Spice must flow                  /
    \______________________________________________________/
A very intelligent turtle
Found programming UNIX a hurdle
	The system, you see,
	Ran as slow as did he,
And that's not saying much for the turtle.