Custom Query (1030 matches)

In a Clozure CL.app built from the event-ide branch:

1. Open a file of Lisp text. Select a range of text
2. Switch to a Listener window
3. Eval uate some form that causes a backtrace
4. Switch back to the editor window

At this point, if the problem has manifested, clicking in the buffer fails to cause the window to update its selection correctly. Typing in the buffer *may* cause the display to return to normal, or it may display a Hemlock error dialog (the "sky is falling" dialog). Generally, some combination of inserting and deleting text seems to eventually cause the window display and event-handling to return to normal.

The Apropos window in the IDE is not a normal window. Instead it is some sort of palette or tool window. (I'm not sure what the correct term is in Cocoa.) This fact gives it two behaviors that I find annoying: (1) it is always on top, and (2) it disappears when I switch to another application.

I can't at the moment think of cogent arguments for why these behaviors are objectively bad, I just know that I run into them and find myself annoyed by them pretty much every time I use the Apropos window.

Printing NSData objects prints out the data contained within them, which is convenient, but it does not obey *print-length*. This gets particularly annoying when working with images, because if one accidentally prints a very large NSData object in the IDE (which often happens during error reporting when such an object has been passed in as an argument), Hemlock chokes, and the only way to recover is to kill the current listener and fire up a new one.