There is an ALTERNATE EDITOR file (I think I got the name right) that
provides a platform independent mechanism for invoking editors (much
as the DEVICE file provides a platform independent mechanism for
working with devices. VistA on GT.M may or may not invoke ZEDIT
"under the hood". Remember that one of the roles of Kernel is to
abstract away from platform dependencies and software written for
VistA shouldn't ever need to use platform specific commands, nor
should users (in principle, at least) need to be concerned about the
underlying platform.
===
Gregory Woodhouse
[EMAIL PROTECTED]
"It is a capital mistake to theorize before one has data."
--Sir Arthur Conan Doyle
On Jun 6, 2005, at 6:16 AM, K.S. Bhaskar wrote:
Ismet --
Set the EDITOR environment variable before starting GT.M to point
to any editor. When ZEDIT "function" is invoked from inside GT.M,
it will start the editor pointed to by $EDITOR, e.g.:
source /usr/local/gtm/gtmprofile
export EDITOR=`which vim`
mumps -dir
GTM>ZEDIT "XYZ"
I am not sure, however, whether VistA invokes an editor with
ZEDIT. I don't know why it is presenting VMSEDT as a choice for
GT.M on Linux. What happens if you take that choice?
-- Bhaskar
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Hardhats-members mailing list
Hardhats-members@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/hardhats-members
