Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!sdd.hp.com!wuarchive!uunet!zephyr.ens.tek.com!tekchips!tekgvs!toma
From: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Newsgroups: comp.lang.lisp.x
Subject: Re: level of nesting in xlisp 2.1
Message-ID: <8581@tekgvs.LABS.TEK.COM>
Date: 12 Dec 90 15:55:26 GMT
References: <1990Dec9.183859.2705@stretch.cs.mun.ca>
Reply-To: toma@tekgvs.LABS.TEK.COM (Tom Almy)
Organization: Tektronix, Inc., Beaverton,  OR.
Lines: 33

In article <1990Dec9.183859.2705@stretch.cs.mun.ca> matthew1@stretch.cs.mun.ca (Matthew J. Newhook) writes:
>Hello:
>    I have several versions of xlisp 2.1, the most recent being the one
>    updated by Tom Almy.  I am running it under several versions of Unix 
>    (SunOS, System V, BSD 4.3), and they all have the same common problem.  
>    They don't show the current level of nesting.
>    ie:
>    if i type
>    >(setq a '(a b c)
>    it should say
>    1>
>    however, it doesn't, it just shows nothing...
>    also a return at the > prompt should return with another >, that
>    doesn't do the job either:

It's not a bug, it's a feature!

The top level of xlisp is roughly:
(loop
	(princ ">")
	(print (eval (read)))
)

READ itself does no prompting, so you only get one prompt for each expression
read.

If you modified the line reading code in the *stuff file then all reading
would be affected, not just that caused by READ. You would have to modify
the READ code to get what you want.

Tom Almy
toma@tekgvs.labs.tek.com
Standard Disclaimers Apply