delorie.com/archives/browse.cgi   search  
Mail Archives: opendos/1997/03/14/12:53:56

Date: Fri, 14 Mar 1997 09:36:39 -0800 (PST)
From: Evan Dickinson <evand AT wsunix DOT wsu DOT edu>
Reply-To: evand AT scn DOT org
To: OpenDOS Mailing List <opendos AT mail DOT tacoma DOT net>
Subject: Re: [opendos] FSSTND
In-Reply-To: <Pine.NXT.3.95.970314015609.6456y-100000@eagle1>
Message-ID: <Pine.OSF.3.95.970314092712.1322A-100000@unicorn.it.wsu.edu>
MIME-Version: 1.0
Sender: owner-opendos AT mail DOT tacoma DOT net

On Fri, 14 Mar 1997 jdashiel AT eagle1 DOT eaglenet DOT com wrote:

> Why not:
> 
> [utility]
> c:\utility
> d:\utils
> [apps]
> c:\dos\apps
> [game]
> c:\games
> 
> This has the advantage of making path additions similar to the way
> they look under dos directory structure.
It's also easier to read than putting them all on one line like I
suggested.

> If a new application were to be installed, it should have a util-type
> tag available for the paths.dir file.
> All paths created on a machine could be documented in paths.dir with a
> [misc]
> tag for those without a defineable type.
> Then with these fast directory changing utilities, moving into
> paths even with five directories dep would be lots easier.

I've got 4dos' cdpath set to work like this.  "Cd telnet" moves me to
c:\dosapps\telnet from anywhere.  Are you suggesting that all paths be put
in a cdpath?  I think that's overkill.  How often do you change to the
djgpp\manifest directory?  Putting the non-misc directories in the cdpath
should be enough.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019