Opened 12 years ago

Closed 10 years ago

#208 closed enhancement (fixed)

Clozure CL.app doesn't load ~/ccl-init.lisp

Reported by: gb Owned by: gb
Priority: trivial Milestone:
Component: IDE Version:
Keywords: Cc:

Description

It should.

(See also ticket:87)

Change History (5)

comment:1 Changed 12 years ago by rme

I suppose that any init file would have to be loaded in or after applicationDidFinishLaunching so that we can display an alert or a backtrace or something if there are errors in the init file.

comment:2 Changed 12 years ago by gb

I think that it would also be good if it loaded in the initial IDE listener (so that it could print things visibly, etc.) This may be a different time than when the IDE customization file loads.

Related question: how should the IDE behave if one starts it by double-clicking on a .lisp source file ? (Should a listener thread/window be created in that case ? Does that happen currently ?)

comment:3 Changed 12 years ago by rme

Double-clicking a .lisp file launches the app and opens the file in an editor window. A listener window is not created.

We may want a listener to be created no matter what. (We could always add yet another user preference, I suppose.)

Here's an idea: if an init file exists, we could create a listener and not order it in. We could then run the init file, and only order in the listener window if something went wrong. If the init file loaded without errors, we could get rid of the listener and the user would never see it.

comment:4 Changed 12 years ago by p2

  • Priority changed from minor to trivial
  • Type changed from defect to enhancement

For delivery (shrink wrapped) CCL apps, a background Listener that loads a broken init file would cause the end user to see what's going on where that might be unwanted. Perhaps there could be a "delivery" config flag to make it an option to suppress this. Or is the idea to condition-bind such things by hand? My vote is for the easy route (the former).

comment:5 Changed 10 years ago by gb

  • Resolution set to fixed
  • Status changed from new to closed

~/ccl-init has been loaded for a fairly long time now; I don't remember when the change was made, but it was pre-1.3.

Note: See TracTickets for help on using tickets.