[Openmcl-devel] Cocoa IDE and ccl-init

[Gary Byers]

It's a bug (sort of related to <http://trac.clozure.com/openmcl/ticket/87>).

It's probably sanest to load ~/ccl-init.lisp (nee ~/openmcl-init.lisp)
in the IDE's initial listener; that's similar to what happens in the
TTY world, so if your init file wants to print messages or request
input (or enter a break loop ...) there'd be a way of supporting that.

There -could- be some sort of well-defined interaction between what's
settable via the preferences pane and what should be defined in the
(to be named) IDE customization file, but it seems to be cleaner
if there was no interaction (e.g., if the preferences system handled
certain things and if the customization file contained things like
custom Hemlock commands and key bindings.)




On Thu, 29 Nov 2007, Ron Garret wrote:

> When I use the self-contained Cocoa app some of the stuff I do in my
> ccl-init file gets stomped on.  Notably, *load-verbose* and *load-
> print* get reset to nil.  This doesn't happen if I start from a
> terminal and do (require 'cocoa).  Is this a bug or a feature?
>
> rg
>
> _______________________________________________
> Openmcl-devel mailing list
> Openmcl-devel at clozure.com
> http://clozure.com/mailman/listinfo/openmcl-devel
>
>