[cells-gtk-devel] Cells-gtk on Lispworks 5.0

[Bill Atkins]

Eh, I'm giving up on this.  I've reached points where I could evaluate
the form more than once from the editor without problems, only to see
it all fail as soon as the IDE got restarted.  I'm not sure what's
going on, but testing at the REPL and a well-placed

 (unless (search "Listener" (mp:process-name mp:*current-process*))
   (error "Can only run from the listener"))

will get me by.  My hunch is that it has something to do with
threading, since the editor spawns a new thread in which to evaluate
forms.

When 5.0 gets a little more momentum, perhaps the problem will get smoked out.

Thanks for the help, Peter and Ken.

On 8/14/06, Bill Atkins <atkinw at rpi.edu> wrote:
> On 8/14/06, Ken Tilton <kentilton at gmail.com> wrote:
> >
> >
> >
> > On 8/14/06, Bill Atkins <atkinw at rpi.edu> wrote:
> > > Hmm.  It now appears that even the demo code won't run after being run
> > > from the Editor once.  I swear it did in the past.
> >
> >
> > I know the feeling. Anyway, it helps to know that.
> >
> > > The bindings for *standard-input* and *standard-output* are indeed
> > > different depending on where the form is evaluated, but they are both
> > > instances of the same class:RUBBER-STREAM.  I guess it makes sense
> > > that they would be different since they're going to different
> > > output-panes.
> >
> >
> > Sure, but I have to think the solution is somewhere in this ballpark. btw,
> > why is it a problem testing from the REPL? Just the inconvenience (which I
> > understand).
>
> Basically.  Once or twice I absent-mindedly evaluated (run-gui) from
> the Editor.  I'd then have to quit LispWorks, start the IDE again,
> bring up the file(s) I was working on, make sure cells-gtk was
> asdf-load'd, and _then_ get back to work.  I guess I could get by at
> the REPL, but I'd rather figure out why this happens.
>
> > > If I wait around a couple of minutes, the Gtk window will come up, but
> > > will refuse to close and GNOME will tell me that it's not responding.
> >
> >
> > OK, is this a change to the problem report? And does this happen reliably?
> > Is the CPU pegged during those two minutes?
>
> I can find out more about this tonight.  It may have been occurring
> all along, but I would always quit LispWorks right after this happened
> and restart, so I would never have noticed it.
>
> > > I haven't had a lot of time to look at this the last few days, but
> > > maybe tonight I'll rummage through the innards of cells-gtk and try to
> > > figure out what's going on.  This is too weird to just let it go.
> > >
> > > (BTW, cells and cells-gtk are pure glory.  Thanks, Ken and Vasilis).
> >
> >
> >
> > You are welcome, and I will update the Cells user count to, lessee, you make
> > 8. :) It will be interesting to see what happens to PyCells by contrast.
> >
> > kenny
> >
> >
> >
>
>
> --
> Bill Atkins
>


-- 
Bill Atkins