15.10.1 New check for Cocoa Event Loop hanging

The LispWorks for Macintosh IDE now has a mechanism that checks for situations where the Cocoa Event Loop is waiting for another process, which gets an error and attempts to raise a notifier window, waiting for the Event Loop to do it, which leads to a deadlock.

When such a situation arises, LispWorks now automatically interrupts the Event Loop so that a notifier appears, the GUI updates and you can then check what went wrong.

15.10.2 Additional notifier controls

For errors in some processes, the notifier window may contain additional controls. In particular on Mac OS X the Error handling in Cocoa event loop : buttons allow you to control error processing in the Cocoa Event Loop (which is the process that does all the display work).

15.10.3 More fonts available in the Editor and other tools

You can now select any available font via Preferences... > Styles > Editor Font in the Cocoa GUI of LispWorks for Macintosh. This font is used in various LispWorks tools including the Editor.

In LispWorks 6.1 and earlier versions, you could select only fonts whose widths are (almost) integral, which is not generally guaranteed.

15.10.4 New Code Coverage tool

The Code Coverage Browser tool helps you to visualize code coverage data and is especially useful when you need to work on the data from many source files.

See Code Coverage for information about the new Code Coverage interface.

15.10.5 Buffers list option in Editor

There is now an option to display a list of buffers in the Text view of Editor windows, facilitating speedy switching between buffers while editing. You can filter the buffers list in the usual way if needed.

To use the new option, select Preferences... > Editor > General > Buffer list > Display a list of buffers in every Editor window .

15.10.6 Preferences option to use quality drawing

Check Preferences... > Environment > General > Use quality drawing to make the LispWorks IDE use quality (anti-aliased) drawing for editor and graph panes. This is the default setting.

15.10.7 Listener current package preserved in Saved Sessions

The Listener tool's current package is now preserved in a Saved Session.

15.10.8 Session saving warns when Debugger or Stepper has state

Session saving now warns if there is a Debugger or Stepper tool with state. This allows you to cancel session saving and complete your debugging or stepping. If you do not want to see this warning again, and always lose the state of a Debugger or Stepper tool when saving a session, check the Do not ask again box in the warning dialog.

15.10.9 Setting breakpoints in the Stepper

The Stepper tool is now better at identifying Lisp definition forms with unexpected indentation. This means that you can now set breakpoints in such definitions.

In LispWorks 6.1 and earlier versions, an unhelpful message

would appear on attempting to set a breakpoint in a definition which was not indented in the conventional Lisp way (as by the Editor command Indent Form).

15.10.10 Tool accelerator keys in KDE/Gnome emulation

Tool accelerator keys (such as Meta+Ctrl+S to raise the Symbol Browser tool) now work on GTK+ in KDE/Gnome editor emulation.

The full set of tool accelerators is documented in the section "Tool accelerator keys" in the LispWorks IDE User Guide .

15.10.11 Find window text pre-selected

Any text in the Editor tool's Find window is now pre-selected on all platforms when the window is raised (typically by menu command Edit > Find... or keystrokes Ctrl+F or Command+F).

Therefore when you want to search for other text, you can now simply type and replace the selection, without needing to take special action to remove the old text.

15.10.12 Search Files tool reports file count after failed search

When there are no matches in the Search Files tool, it displays a message which now mentions the number of files that were searched.

15.10.13 Menu command to install private patches on Windows

On Microsoft Windows the menu command Help > Install Private Patches... should now be used to install private patches (that is, named patch files sent to you by Lisp Support).

15.10.14 Erroneous restart removed

The restart "Edit the code where the error occurred" is no longer erroneously offered when the system does not know where the source is, such as when a buffer that has never been saved to file gives an error in the Editor.