Major issue: There is a general issue about how these menus fit in with the menus that
might be provided by the underlying toolkit. For example, under what circumstances is CLIM
allowed to directly use the menu facilities provided by the host? Should :leave-menu-visible t
interact with the "pushpin" facility provided by OpenLook? | SWM

=> menu-choose items &key associated-window printer presentation-type default-item default-style
label cache unique-id id-test cache-value cache-test max-width max-height n-rows n-columns x-
spacing y-spacing cell-align-x cell-align-y pointer-documentation [Generic Function]
Displays a menu whose choices are given by the elements of the sequence items. It returns three
values: the value of the chosen item, the item itself, and the pointer button event corresponding
to the gesture that the user used to select it. If the user aborts out of the menu, a single value
is returned, nil.

items is a sequence of menu items. Each menu item has a visual representation derived from a
display object, an internal representation that is a value object, and a set of menu item options.
The form of a menu item is one of the following:

• An atom. The item is both the display object and the value object.
  
  
• A cons. The car is the display object and the cdr is the value object. The value object
  must be an atom. If you need to return a list as the value, use the :value option in the list
  menu item format described below.
  
  
• A list. The car is the display object and the cdr is a list of alternating option keywords
  and values. The value object is specified with the keyword :value and defaults to the
  display object if :value is not present.

• :value - specifies the value object.