Re: Sig vs. Xy4

["..." adpf@xxxxxxxx]

≪Try a .kbd entry like ...
	nn=SI,{,m,d,n,m,},CI
... ( {}=CtrlShift 174-175 ) and see if v4 will place the entry *in text
or on CMline*. ≫

≪	It puts it on the CMline, but if you precede it by a GT it puts
it in text. ≫

Harry--???

My point--emphasized--was that one v3 key puts a mode on the CMline or in
text. Two keys for each of 10 modes? I don't think so. Also, I assume
that you did your test in expanded view. In v3 the sequence also works in
draft or expanded. But, as I said, v4 giveth and v4 taketh away. Once you
get {mdXX} on the CMline, v4 will find in draft view; v3 won't.

Single-key v4 CMline or text mode entry can be done with a .KB4 sequence
plus a .U2 macro. v4 doesn't much like mine--which ignores the initial
view and after XP defaults to draft view--and neither do I. I can't test
a more generic one now since a hdd problem has disabled my xyDos 4 but,
if v4 va$ and skeletal function documentation can be trusted (my
experience is that view func documentation is unrelated to reality), this
should work:

.KB4:
	nn=JM,(,2,.,n,m,)

.U2:
	{{5,nm}}
	[asc002]{sx13,{va$dt}}XP {sv86,{mdnm}}{gt86}{if{is13}=="0"}{ex}
	{ei}{if{is13}><"4"&{is13}><"12"}WG {ex} {ei}WZ {ex}[asc002]

Multiply by 10. Documentation on view function(s) that might restore the
original marker and page-break state is hopeless. ... Ciao. 	--a

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