#Slippery Path
5 messages in this thread
If I use a command like
PATH SC: ADD
in a script that executes and then closes its own CLI,
the path is not affected for subsequently opened Shells.
Is there any way to change the system path on a global basis
besides modifying the Startup-Sequence?
I have tried modifying my Shell-Startup file, but this is
undesirable because SC: is on a removable SyQuest cartridge that
is usually not mountaed at boot time.
Any ideas?
Mike,
I believe that the command is operating as per the manual. Adding the
command to the startup sequence (or USER-STARTUP) is the best way to
overcome your problem.
You might try using the "QUIET" option on the command, this should
avoid the requesters for the "missing path" if it is not mounted at the
time the command is issued. (I must admit not having attempted this but it
is the message I get from reading the manual. Worth a try?)
regards Leonard.
Mike,
Forget my last message re using Quiet. It only works with the SHOW
option after the paths have been defined. Well that how it looks now that
I have tested it.
Another suggestion,
Write a script that checks if the volume is present and if so ADD the
part. This could be added to your Shell-Startup without problems.
regards leonard.
Shells either inherit their paths from their parents (if you start one
shell from another) or from the paths in effect when the LoadWB command is
executed (if started from the Shell icon). For the latter type of Shells,
you can use the LoadWB NEWPATH command. Workbench will re-snapshot its
paths from the paths in effect in that Shell.
Any shells that are already up are going to have to have the path added by
hand, of course.
andy *s
Mike;
ASSIGN SC: <syquest:directory> DEFER
PATH <syquest:directory> QUIET
Should do what you want.
-bill