To: evand AT scn DOT org
Cc: opendos AT delorie DOT com
Subject: Re: FSSTND
Message-ID: <19970508.202215.5191.0.chambersb@juno.com>
References: <Pine DOT OSF DOT 3 DOT 95 DOT 970508111337 DOT 1046A-100000 AT unicorn DOT it DOT wsu DOT edu>
From: chambersb AT juno DOT com (Benjamin D Chambers)
Date: Thu, 08 May 1997 23:26:05 EDT
Precedence: bulk


On Thu, 8 May 1997 11:37:40 -0700 (PDT) Evan Dickinson
<evand AT wsunix DOT wsu DOT edu> writes:
[snip]
>Or, *like we already discussed*, we could put the directories into a 
>file
>(paths.dir).  This would look something like: 

That's not the point - the feature of interest is later in the message,
this just sets up the stage.

>This list has been around for a while now.  There's alot that's been
>discussed.  Instead of re-inventing the wheel every two months, I'd
>encourage you to read the mailing list archives
>(www.delorie.com/opendos/archives) and build from what's already been
>discussed.
Umm... Hello?  I _did_ spend a bit of time discussing it previously... 
See above...

>> It could, say,
>> 	Error: TMP_DIR not set.
>> 		1 - Abort
>> 		2 - Enter path manually
>> 		3 - Enter path and set to TMP_DIR
>> 		4 - Use another FSSTND path
>> 

>Which would have the side-effect of plastering that over whatever 
>pretty
>interface the programmer made.  You could let the *program* choose 
>from
>those options (and have it get the needed user input itself).

And what does 'Abort/Retry/Fail' do right now?  I'm proposing a seemless
way to deal with all these path's - Otherwise, when a program needs a
path that's not available, it might just guess what to use (which takes
us right back to the same old mess).




This message brought to youby the user of a Dvorak Keyboard :)
...Chambers