nagy%warner.hepnet@LBL.GOV (Frank J. Nagy/VAX Guru) (10/20/87)
>Well, the original question hasn't been answered yet: >>How would one define MAIL$EDIT so that the whatever/EDIT commands would work? >That is, how to send AND read mail using the same editor interface, not just >the same editor. E.g. my MAIL$EDIT points to a EDTINI.EDT file in a group's >common directory, which defines a number of additional keys and such. >So how does one cause CALLABLE_EDT to execute a specific startup file? >(BTW, DEFINE CALLABLE_EDT <my-usual-EDTINI.EDT> and > DEFINE MAIL$EDIT CALLABLE_EDT doesn't work :-) ) Define the logical name EDTINI to point to your EDT startup file: $ DEFINE EDTINI SYS$LOGIN:EDTINI.EDT !For instance Then your EDT keys and macros will be defined no matter what your current directory is; these same definitions will also be in effect in EDT when it is called from MAIL (by defining MAIL$EDIT as CALLABLE_EDT). Similarly, for LSE, I have my initializations embedded in a section file which I reference by the logical name LSE$SECTION. This then works no matter what directory I'm in and in MAIL-called LSE (by defining MAIL$EDIT to be CALLABLE_LSE). Similar actions can be taken for TPU. = Frank J. Nagy "VAX Guru" = Fermilab Research Division EED/Controls = HEPNET: WARNER::NAGY (43198::NAGY) or FNAL::NAGY (43009::NAGY) = BitNet: NAGY@FNAL = USnail: Fermilab POB 500 MS/220 Batavia, IL 60510