Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uflorida!gatech!rutgers!att!pegasus!ech
From: ech@pegasus.ATT.COM (Edward C Horvath)
Newsgroups: comp.sys.mac
Subject: Re: TEKey and other word processing data structures
Message-ID: <2722@pegasus.ATT.COM>
Date: 27 Mar 89 19:49:45 GMT
References: <11116@well.UUCP>
Organization: AT&T ISL Middletown NJ USA
Lines: 25

In article <28542@ucbvax.BERKELEY.EDU>, usenet@ucbvax.BERKELEY.EDU (USENET News Administration) writes:
> From: thom@dewey.soe.berkeley.edu (Thom Gillespie)
> Path: dewey.soe.berkeley.edu!thom
> 
>I've been plauing with the miniedit program in LSC and I can't figure how
>to force a line feed. I've been tying TEKey('\$0D',TEH) and variations on
>'\0D' but the best I get is a square box non-printing indicator. Waht am I
>doing wrong.

Try using '\015' for carriage return.  C was invented back when octal was
still all the rage...

Also, I notice in the MPW C 3.0 that the definitions of \n and \r have been
interchanged from the "normal" values.  This actually makes a perverse kind
of sense, if ALL you ever code is \n as a newline.  LSC hasn't taken this
step, so you could also use
	TEKey ('\r', TEH);
at least until LSC decides to become MPW compatible (yech).

To their credit, at least MPW 3.0 uses all lower case trapnames for the
ones with cstring braindamage, and mixed case for the "real" (minimum glue)
trapnames.  AND they provided a tool (CCvt) for converting from the old
convention to the new one.  As I've said elsewhere, MPW 3.0 is a class act.

=Ned Horvath=