🚀 go-pugleaf

Today I started experimenting with read-only zones in Epoch 4.2 and I
immediately found three bugs!  How discouraging :-(.

  + The documentation refers to the function "epoch::zone-read-only", but the
    real name is "epoch::zone-read-only-p".  The wrapper is misnamed, too.

  + The function epoch::set-zone-read-only changes the value of the current
    buffer's read-only button count, not the count for the zone's buffer.
    (This was quite confusing, as I was entering forms in the *scratch* buffer
    to manipulate a zone in another buffer.  I made my test zone read-only, but
    it didn't actually become read-only until I made another call to
    epoch::move-zone.)

  + I set the style of my read-only zone to include an underline.  I have found
    that when I insert a character immediately before the zone, that new
    character is underlined (but is apparently not in the zone?).  At the next
    event (e.g., hitting the Control key) the underline beneath the new
    character disappears.  Hitting two characters in a row results in the first
    being temporarily underlined; when the second character is inserted the
    underline for the first character disappears.

--
-------------------------------------------------------------------------------
Eric Eide          |          University of Utah Department of Computer Science
eeide@cs.utah.edu  | Buddhist to hot dog vendor: "Make me one with everything."