🚀 go-pugleaf

Bill Harvey (HARVEY@WUVMD.BITNET) wrote:
:    [ RM excerpt ]
: That tells me that "while the macro is running" XEDIT isn't "in" input
: mode.  So there's no problem.

: Maybe the question is:  "How can the macro insure that XEDIT doesn't
: *reenter* input mode when the macro ends?"  Queueing the null line
: will take care of that very nicely.

: I don't see why you'd want to requeue the macro command.  While the
: macro is running, you're "in edit mode."  At least, I can't see
: any practical distinctions between the two modes from the macro's
: point of view.  Maybe I missed something obvious.

Yes.  I have two files in a ring; I'm in input mode in one of them.  I wish
to glance at the other briefly, then return to input mode on the first.
I set a PF key simply to "XEDIT".  Unfortunately, when I press this key,
I find myself in the second file, but _in_input_mode!_  

It strkes me as a colossal design blunder that input mode is a global
attribute of the entire XEDIT session, rather than local to an individual
file within the ring.  What do others think?

(Actually, if I recall correctly, the present behavior is an innovation;
around CMS 3, I believe, pressing a PF key while in input mode caused
_the_definition_of_the_PF_key_to_be_input_as_text!_)