CompuServe Messages

Mark, WShell comes back to life as soon as you click on its icon — it just reloads the library from LIBS:. If you put commands in your s:startup-wshell file to load the resident commands, it will re-do the resident list when you next open a WShell. It doesn't really hurt anything to have the library expunged from memory, but just takes a little longer to reload it. I'm thinking of adding a "lock in memory" flag to keep WShell from being expunged, so the user will have more control over the issue. The WShell update is still under development but will be announced fairly soon; I'm also planning to extend the ARexx update policy to WShell, since people seem to like it pretty well. No timetable yet for ARexx update — will turn my attention there once WShell is squared away.