Re: Hellp request: non-break blocks; hard spaces

[Carl Distefano CLDistefano@xxxxxxxx]

** Reply to note from Eric Van Tassel <101233.342@xxxxxxxx>
** Fri, 21 Mar 97 07:41:06 +0000

-> Can the collective wisdom assist me with two problems whose
-> solutions are probably staring me in the face?

-> (1) Non-breakable blocks:
->
-> Why don't my non-breakable blocks break? 

If you mean your NB blocks are breaking when they shouldn't, try
extending the begin and/or end point of the block (by moving the NB
and/or BB commands, of course). You can usually jiggle it to achieve
the desired result. (There's some kind of funny interaction between
NB...BB and certain combinations of BT, WD, OP and possibly other
formatting values that causes NB blocks to break sometimes. I never
tried to investigate why this happens; I just work around it.)

-> (2) Hard space ASCII 32:
->
-> I haven't been able to write an XPL routine that will accept
-> ASCII 32 on the command line, even though I can input it on the
-> command line manually.

The hard space is not Ascii-32; it's a 3-byte character consisting of
Ascii-255 plus "20" (i.e., the hexadecimal equivalent of 32).

The short answer to your question is another question: If you're in
Xy4 or XyWin (and you probably are, if the hard space displays as an
inverted triangle), why use the command line at all? Use Blind Execute
(func BX)! For example, to search for the hard space from top of file:

 BX (se/t #)

where "#" stands for the hard space as you would normally input it.

If you absolutely must get the hard space on the command line, the way
to do it is:

 GH 

where the "space" in  is actually a 3-byte Ascii-255. (To produce
a 3-byte 255, execute funcs R2 R5 R5 NO; with XY4.KBD loaded, hold down
Ctrl-Alt-Shift and press 2,5,5.)

To understand why this code works, read Holmgren's CTRLCHAR.TXT.


--------------
Carl Distefano  * * *