rkl@and.cs.liv.ac.uk (02/11/91)
In article <795@utrcu1.UUCP>, kortink@utrcu1.UUCP (Kortink John) writes: > dhmyrdal@lise.unit.no (Dag Haakon Myrdal) writes : > >> (For those having access to a VAX: yes, this is similar to the way >> the VAX handles file version-numbers) > > Personally, I find VAX's version numbers a pain in the ***. Version numbers are a BRILLIANT idea, sorry folks ! I have a symbol set up to do a RENAME *.*;* *.*;1 (after a PURGE of course) just to keep the numbers neat. What I *don't* like about VMS's filenames is that you can't have mixed case at all (I would still retain the *excellent* idea (ADFS has this too) of case-insensitivity when actually specifying filenames). > But unlimited length (well, up to disc space at least :-) filenames a-la > Unix would be great. What I *hate* about UNIX filenames (apart from case-sensitivity when you need to use the name) is that they very, very, very STUPIDLY allow control characters to be embedded in them. This is completely crazy and flummoxes many students at our site. 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 ? :-) Richard K. Lloyd, **** This is a MicroVAX II running VAX/VMS V5.4 **** Computer Science Dept., * JANET : RKL@UK.AC.LIV.CS.AND * Liverpool University, * Internet : RKL%and.cs.liv.ac.uk@cunyvm.cuny.edu * Merseyside, England, **************************************************** Great Britain. Q: "What's the world's fastest home micro ?" L69 3BX A: "The Archimedes A3000. 4 MIPS for under 800 pounds." ^ This price includes VAT and a cheap monitor, I guess ---------------|
rhh88@ecs.soton.ac.uk (Heywood RH) (02/12/91)
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.
hughesmp@vax1.tcd.ie (02/13/91)
In article <1991Feb11.100559.15181@and.cs.liv.ac.uk>, rkl@and.cs.liv.ac.uk writes: > In article <795@utrcu1.UUCP>, kortink@utrcu1.UUCP (Kortink John) writes: >> dhmyrdal@lise.unit.no (Dag Haakon Myrdal) writes : >> >>> (For those having access to a VAX: yes, this is similar to the way >>> the VAX handles file version-numbers) >> >> Personally, I find VAX's version numbers a pain in the ***. > > Version numbers are a BRILLIANT idea, sorry folks ! I have a symbol set up > to do a RENAME *.*;* *.*;1 (after a PURGE of course) just to keep the I think they are really annoying too (ps. you can make that a RENAME *.* *.*); they make accessing files just too niggly. I am sure it is great, in that it means you don't lose old copies of a program by accidentally saving new ones, unless you specify that you want no backups when you create the directory. I like to be able to save old copies if _I_ want to, not delete them if I don't want them. > 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 ? :-) It is. Surely however, you could superficially get around this in the Desktop by rewriting the ADFS Filer, so it gave files id numbers or something instead of names, and then had a file (like the Mac desktop file. Bleech.) which had the corresponding names for id numbers. That'd be fun to write, wouldn't it. Although the problem is really for use with the CLI; how about rewriting the ADFS yourself someone? (Keeping compatibility with the Acorn ADFS would be a big problem tho'...; that is one thing, if anything like this was done, it would _have_ to be backwards compatible to an extent; otherwise you would get major problems with obsolete A3000s I suspect, which would make a _real_ implementation of it quite difficult... And how many programs limit the filename to ten characters _themselves_?) T.
hughesmp@vax1.tcd.ie (02/14/91)
In article <6733@ecs.soton.ac.uk>, rhh88@ecs.soton.ac.uk (Heywood RH) writes: > 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! Just a point, in case you don't know it; the utility !LineEdit by Richard (RKL) supports this very feature; as opposed to Escape, however, you hit tab, and it will complete the filename, or if there are ambiguities, will go as far as it can, and then beep. The utility itself alters the operation of the COPY and arrow keys, giving a VAX-style way of recalling past lines, and editing the lines with the left and right arrows... This is very useful for doing CLI based stuff, but I find gets in the way a bit when programming. Just in case you didn't realise... T.
dhmyrdal@lise.unit.no (Dag H}kon Myrdal) (02/20/91)
In article <1991Feb13.133453.7780@vax1.tcd.ie> hughesmp@vax1.tcd.ie writes: [references to lots of articles deleted...] >I think they are really annoying too (ps. you can make that a RENAME *.* *.*); >they make accessing files just too niggly. I am sure it is great, in that it >means you don't lose old copies of a program by accidentally saving new ones, >unless you specify that you want no backups when you create the directory. I >like to be able to save old copies if _I_ want to, not delete them if I don't >want them. It seems that my proposal has been misunderstood by several of the people that have written their comments... I *did not* propose version numbers in ADFS, just that we should be able to treat *filetypes* like one can treat version-numbers on VAX... ie: if you want to *access* the text-file @.file, you should be able to write: either "@.file" OR "@.file#FFF" OR "@.file#text"... Also, ADFS should be able to handle several files in the same directory having the same filename, but different filetypes! (And it was *here* I pointed out that this was done similarly on the VAX) - Hope this is clear now ? >It is. Surely however, you could superficially get around this in the Desktop >by rewriting the ADFS Filer, so it gave files id numbers or something instead >of names, and then had a file (like the Mac desktop file. Bleech.) which had >the corresponding names for id numbers. That'd be fun to write, wouldn't it. OK, it would be fun to write, but a bloody mess to use :-) Remember, that a Mac-user can be fooled by the desktop quite easy, but a Arc-user will often use the CLI, too.... Just imagine the confusion of having one way of having filenames in the desktop, and a completely different way using the CLI... >And how many programs limit the >filename to ten characters _themselves_?) Noone, I hope! This is a task for the OS, and besides, programs should enable you to write pathnames+leafname, which can be 256 chars! --Dag H. Myrdal