Re: va$nw ? [was va$wn ?]

["..." adpf@xxxxxxxx]

≪	Like Robert, I'm not clear on what you mean by "freeze". ≫

Hi, Carl. I think Robert's question may have allowed other
interpretations ;) , but what I meant is that the system stops dead.
xyW won't respond to ES or BK or anything but C-A-D. I probably
reloaded it three dozen times trying to get that single instruction ...
	{sx86,{va$nw}}
... to work.

≪	When you say, "A solution that involves the use of va$wa is
unacceptable to me since it precludes use of d nw=0", what is the
problem you're trying to solve? And how does VA$WA preclude D NW=0? ≫

When I asked, I thought va$nw must have disappeared from v4, and was
wondering what alternatives were available. But va$nw works for others
and I've since discovered that an equally innocuous instruction in old
code also acts up now, so I feel sure that my installation is at fault.
(I suspect that NU has strewn EDITOR all over a partition that is about a
quarter bad clusters--marked, of course--and can't be fully defragged
now). I've had no occasion to use va$wa, but trusted CG p234. CG may be
in error or maybe I'm misinterpreting this, but it seems pretty
straightforward:

"VA $WA [...] Displays the number of the next available window that
XyWrite will use when a CALL or NEW command is executed. (The NW default
must be set at 1, 2, or 3.)"

I'd wondered what the distinction was between VAs that do and don't have
a $, but haven't got into v4 xpl enough for it to matter. I'm glad to
read an explanation.

≪	Now, what was the question? ≫

A koan? 	--a

============================= adpFisher  nyc