Path: utzoo!utgpu!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!rutgers!rochester!pt.cs.cmu.edu!andrew.cmu.edu!bader+ From: bader+@andrew.cmu.edu (Miles Bader) Newsgroups: comp.sys.amiga Subject: Re: path: & 1.3 (also RAD: recovering) Message-ID:Date: 6 Dec 88 08:34:57 GMT References: <284@gtss.UUCP> <385@solaria.csun.edu>, <286@gtss.UUCP> Distribution: na Organization: Carnegie Mellon Lines: 26 In-Reply-To: <286@gtss.UUCP> chas@gtss.UUCP (Charles Cleveland) writes: > In article <385@solaria.csun.edu> ecphssrw@trantor.csun.edu (Stephen R. Walton) writes: > )Possible commercial announcement: Bill Hawes says over on BIX that he > )has finished a similar Path-Handler which will come with the next > )update of WShell. It allows you to simply say: > ) Assign C: Sys:c,df0:c,df1:c > )(for example). You can also do a Dir C: with his handler, and get the > )result you expect, rather than an infinite stream of "Unknown Packet" > )errors. > > Will it support > Assign L: sys:L, wp:L, Lattice_C_5.0.1:L ? > > That is, does the search extend beyond that for commands, but to other > referenced files as well? What are the limits on what's passed as the name of a file? If it's possible, I'd like to see a path device that works something like (e.g): assign c: path:sys:c/,mydisk:c/ makes looking for a file on c: look in sys:c and mydisk:c So can you pass ":" and ","? And what are the name length limits? -Miles