[Gcl-devel] Re: readline and axiom

[Camm Maguire]

Greetings!

"Page, Bill" <address@hidden> writes:

> Camm,
> 
> Is it usual for GCL to ouput a long stream of messages
> following the
> 
>   (si::init-readline)
> 
> call? What I see when I start the --endable-static image
> that was generated during the Axiom build after the
> (si::init-readline) is
> 
>   starting address -T 0x86b04c0 Finished loading ... gcl_readline.o
>   T
>   "Gcl"
>   1
>   (":INTERN: ":STEP" .....
> 
>    etc. for about 200 lines of output or so
> 
>   ... "PUSH-OPTION-BINDING")
> 

This is normal for the current readline implementation.  The symbols
are those in the current package which could be available from
command-line completion.  We could silence this I imagine.

I'd be most interested if you find any instability (e.g. segfaults) in
a static readline build.

Take care,

> After which readline actually does behave as I had
> hoped and allows me to edit.
> 
> Regards,
> Bill Page.
> 
> On Tuesday, October 28, 2003 12:30 PM I wrote:
> > 
> > On Tuesday, October 28, 2003 12:03 PM you wrote:
> > 
> > > ... readline library must be initialized at runtime via
> > > the lisp command:
> > > 
> > > (si::init-readline)
> > > 
> > ... 
> > > Would be nice if you could report any readline functionality
> > > differences between the to ports, if any. 
> > > 
> > 
> > Well, I did observe that when I start GCL 2.6.1 on windows,
> > I don't have to do anything to start readline. So I guess
> > the (si::init-readline) got executed somehow but it is not
> > in the GCL.BAT startup file.
> > 
> > I'll let you know more once I actually see it work
> > under Linux.
> > 
> > Cheers,
> > Bill Page.
> > 
> 
> 
> 
> 

-- 
Camm Maguire                                            address@hidden
==========================================================================
"The earth is but one country, and mankind its citizens."  --  Baha'u'llah