🚀 go-pugleaf

>Fine, thinks I, but the timer isn't the best way to do things -- it burns
>cycles when not needed, and doesn't when it is (ie you can say SET
>DEFAULT [BLAH] and not see the new prompt until the next time you hit
>Return).

I too was a bit concerned about the timer and kludgy results of setting default
early in the timer interval.  (ie. the default may be changed but the prompt
may not reflect it. Ref:. the comment preample in the published code)

>What I do is re-vector SYS$SETDDIR to point to the code in P1 pool, so
>that after each call to $SETDDIR, the prompt is updated.

>The only snag at the moment is that the routine runs in the access mode
>of the caller, which means it may or may not be able to fiddle the
>prompt.  Usually, it will run in supervisor mode (ie when called from
>DCL as a result of a SET DEFAULT command), but if a user mode program
>decides to change the default directory, the prompt won't be updated.

>Anyone have a good solution to this problem?  (It's 5am and I'm off to
>bed!)

YES-

Make your thread of code into an executive mode (user defined) system service.
Then 're-vector' SYS$SETDDIR to point to the new service instead of code in P1
pool.  The code under the new service can then run in EXEC mode.

BJS-