[Openmcl-devel] Hemlock ain't Fred

[Gail Zacharias]

I see you found the answer, but just a caveat: I'm working on 
changing all this.

Basically, as http://trac.clozure.com/openmcl/wiki/CocoaIdeInternals 
explains, Hemlock was written for a single-window single-process 
environment, so something had to change to integrate it into 
OpenMCL/Cocoa.  The particular way it was done is turning out to be 
too fragile, so I'm working on plan B.  Editor commands will be 
executed in the Cocoa event thread.   hi::*buffer-gap-context* is 
going away.  There will be a user-friendly with-buffer macro if you 
want to do stuff to a buffer outside the command execution context.

Gail

At 10/30/2007 02:56 AM, Ron Garret wrote:
>I'm trying to manipulate Hemlock windows in the new IDE the way I used
>to be able to manipulate Fred windows.  Turns out I can't just do e.g.
>
>(insert-string mark string)
>
>Instead I have to do this:
>
>(let ((HEMLOCK-INTERNALS::*BUFFER-GAP-CONTEXT* (hi::buffer-gap-context
>(line-buffer (mark-line mark)))))
>   (insert-string mark "foo"))
>
>which is not a show stopper, but it's damned annoying.  What is this
>*BUFFER-GAP-CONTEXT* thing and why isn't it bound automatically?
>
>rg
>
>_______________________________________________
>Openmcl-devel mailing list
>Openmcl-devel at clozure.com
>http://clozure.com/mailman/listinfo/openmcl-devel