| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 537.1 | | WJG::GUINEAU | | Mon Aug 24 1987 15:35 | 5 |
|
Write a Condition Handler, enable it and then (from inside the CH)
use $GETMSG or $PUTMSG to intercept system messages...
|
| 537.2 | I did it in SMG$, easy! | ANGORA::ZARLENGA | Living on the hedge ... | Mon Aug 24 1987 17:42 | 7 |
| SMG has some easy-to-use built in functions for just this
sort of thing.
Check out Volume 5D (in v4.0 manuals) - or around there if
your set is newer.
-mike
|
| 537.3 | nothing whatsoever to do with hackers | PUGH::JUSTINC | | Wed Sep 02 1987 10:43 | 8 |
| I know that this has nothing to do with hackers etc but could anyone
out there mail me some prompts????
Please!!!!
thankya very much
justinc
|
| 537.4 | What's in a name? | MDVAX3::COAR | A wretched hive of bugs and flamers. | Tue Dec 15 1987 08:59 | 6 |
| If you mean broadcast messages, use SMG. If you mean error messages,
use .1.
Re .3: Mail you some prompts? What do you mean?
#ken :-)}
|
| 537.5 | A 'prompt' answer !! | CHEFS::VEALES | Simon Veale - DEC Park, Reading | Tue Dec 15 1987 09:52 | 10 |
|
Re .3: Lots of people write themselves command procedures which
set their terminal prompt to something 'unusual', pictures
usually.
Why not look in RDGENG::COMMAND_PROCEDURES, I'm sure I've
seen some there.
S.
|