B From:	MERC::"uunet!WKUVX1.BITNET!MacroMan" 23-MAR-1993 09:00:12.36 To:	MACRO32@WKUVX1.BITNET  CC:	2 Subj:	RE: How to intercept keystrokes while in DCL  M In article <930322081847.707@VESTA.SUNQUEST.COM>, <GAVRON@VESTA.SUNQUEST.COM>   writes:A >         Anyway, the answer to your question is that you need to @ >         patch DCL, otherwise you have no way of knowing if the? >         keystroke you intercept is for DCL or an application.   J Ohhhh, I dunno.  Not if you intercept between the typeahead buffer and the terminal driver read buffer.   Hint:  IRP$B_RMOD.  J You still don't know whether it's a DCL command or input to something like" REQUEST or READ SYS$INPUT, though.   > [...] 6 > In other words, your command-line-completion routine# > needs to know DCL inside and out.   $ This problem still remains, however.  M Personally I think it would make more sense to build a character-cell-capable M visual shell.  I'll bet you could build something that most programmers would H be happy with and eliminate about 90% of the need for manually-typed DCL	 commands.   =         --- Jamie Hanrahan, Kernel Mode Systems, San Diego CA O drivers, internals, networks, applications, and training for VMS and Windows NT M uucp 'g' protocol guru and release coordinator, VMSnet (DECUS uucp) W.G., and J Chair, Programming and Internals Working Group, U.S. DECUS VMS Systems SIGB Internet:  jeh@cmkrnl.com  Uucp: uunet!cmkrnl!jeh  CIS: 74140,2055