OS/2 Shareware BBS: 6 File/06-File.zip/go_v241.zip/GO.DOC

Text File | 1994-12-16 | 4KB | 82 lines

------------ GO v2.41 CWD utility for DOS and OS/2 by Adam McKee ------------

GO is a small, relatively simple program intended to relieve you of the task
of typing really long pathnames when you want to change your CWD.
GO is not intended to replace the CD command.  Instead, it should be used
only when it will provide more convenience than the CD command.  I think
you will find that it is often more convenient to use GO.

Instead of giving an in-depth discussion of GO's operation, I will simply
give you a few examples.  You should be able to learn how to effectively use
GO from these examples.  The examples will take the form:

DESTINATION: C:\GAMES   [DESTINATION: desired path]
D:\> GO C./GAM          [X:\> command given to interpreter]

DESTINATION: c:\os2\system
C:\> go os2.sys

DESTINATION: c:\os2\system
D:\> go c.os.sys

DESTINATION: C:\bc
C:\UTILS\BC\TVISION\INCLUDE\> go ..

DESTINATION: C:\UTILS\BC\INCLUDE
D:\> go c.ut.bc.inc

You should get the idea by now.  Remember that GO is not psychic.  If there
is more than one match for the pattern you specify, GO will not be able to
determine which path you want, and it may choose the wrong one.  If you find
that GO chooses the wrong directory, try giving it a little more text to work
with (another 1-2 characters will usually do the trick).

-- DOS Setup: ---------------------------------------------------------------

Just copy GO.EXE to a directory that is in your path.

-- OS/2 Setup: --------------------------------------------------------------

First, copy GO.CMD and GO_MAIN.EXE to a directory that is in your path.
Then, you must edit GO.CMD.  Here is what it looks like initially:

@C:\OS2\APPS\GO_MAIN.EXE C:\OS2\APPS\GO.CMD %1 %2 %3 %4 %5 %6 %7 %8 %9

<< if you have placed GO.CMD and GO_MAIN.EXE in C:\OS2\APPS, you actually
   don't need to edit the file at all, and you can stop reading >>

GO.CMD calls GO_MAIN.EXE (using its fully qualified path), and gives ITS OWN
PATH as the first argument.  Any arguments given by you come afterward.
To edit this file to work with your particular setup, just change the paths.
For example, if you have placed GO.CMD and GO_MAIN.EXE in C:\OS2, the GO.CMD
file should look like this:

@C:\OS2\GO_MAIN.EXE C:\OS2\GO.CMD %1 %2 %3 %4 %5 %6 %7 %8 %9

You may ask: why is GO.CMD needed?  Whenever a process that is launched from
the shell exits, the shell's environment is restored to its state prior to
the process's execution.  Since the CWD is in the environment, any changes
made to this variable by a process will simply be undone when the process
(i.e. GO) exits.  So, GO.CMD is required to serve as a 'go-between':
GO_MAIN.EXE places a 'CD' command in GO.CMD, so that it can be run by the
shell after GO_MAIN.EXE exits.  GO.CMD gives GO_MAIN.EXE its fully qualified
path so that GO_MAIN.EXE can access GO.CMD and make changes to it as required.

------------------------------------------------------------------------------

For more information, run GO with no arguments.

------------------------------------------------------------------------------

GO is FREEWARE.  As such, you are not obliged to make any payment to me in
exchange for the use of it, and it is not `crippled' in any way whatsoever.
However, if you find GO useful, and you would like to send me $5 CAN to
reward my efforts, please do so!  Any suggestions you have for improving
GO will also be appreciated.  Here are my physical/virtual addresses:

    Adam McKee            Internet: [e-mail]
    2335 Lansdowne Ave.
    Saskatoon, Sask.
    S7J 1G8
    CANADA