Re: lib$spawn particulars
From: Thien-Thi Nguyen (ttn_at_glug.org)
Date: 12/09/03
- Next message: RC Bryan: "Re: porting problems encountered"
- Previous message: Guy Peleg: "Re: Another DCL request: A way to get the .dir of the current directory"
- In reply to: Bob Koehler: "Re: lib$spawn particulars"
- Next in thread: briggs_at_encompasserve.org: "Re: lib$spawn particulars"
- Reply: briggs_at_encompasserve.org: "Re: lib$spawn particulars"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 09 Dec 2003 12:17:43 -0500
koehler@eisner.nospam.encompasserve.org (Bob Koehler) writes:
> Just make sure sys$output and sys$command are
> what you want them to be.
thanks for the tip. i had not thought about this.
> Do you map the PTY to an
> emacs window?
yes, this is the so-called shell (asynchronous DCL)-in-a-buffer feature.
i notice that "logout/full" displays extra summary info. would it be
correct to say that the ast call and event flag setting occur *strictly*
after this output?
> You may need to clean up the PTY, use "SHOW SYSTEM" to
> make sure that the subprocess really exited. In particular if you
> used a mailbox you never read the subprocess might be in RWMBX.
i see the subprocess has exited; it is the parent that is in LEF state.
thi
- Next message: RC Bryan: "Re: porting problems encountered"
- Previous message: Guy Peleg: "Re: Another DCL request: A way to get the .dir of the current directory"
- In reply to: Bob Koehler: "Re: lib$spawn particulars"
- Next in thread: briggs_at_encompasserve.org: "Re: lib$spawn particulars"
- Reply: briggs_at_encompasserve.org: "Re: lib$spawn particulars"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]