Known Bugs

This isn't a bug actually:  The grep string /\(^.*\n\)\1/\1/ should find pairs
of identical lines and eliminate one of them.  But in Uedit's grep you can
only use the carat ^ (force match to start of line) as the very first thing
in grep strings.  I did this on purpose to encourage people to type in an eol
instead of using the carat; searching for an eol is faster than testing for
start of line.  Only at the front of the string do you need to use the carat
to force a match to start of line, and only then because at start of file
there is no eol before the beginning of the line.  To find pairs of identical
lines and eliminate one of them, use this grep string:
        /^\(.*\n\)\1/\1/

When you search with the above command and find a match, only 1 line is
colored because only the cursor line gets refreshed.  To make it color both
matched lines, you must add a refreshDisplay to the virtual-f10 command.

Title Bar with 1 bitplane:  When you switch to a 1 bitplane screen the title
bar is left blank.  If you go to/from tiny window, the title bar is updated,
however, and behaves correctly thereafter.  This bug only happens with
Workbench 2.0.

If you press the menu button to display a menu, sometimes the menu may be
chopped off by Uedit.  This is a cosmetic bug and you can get the full menu
displayed again by reselecting the menu with the mouse.

((In Workbench 1.3 there was a handy menuDrawn flag in the private area of
the Intuitionbase structure which was elminated in Workbench 2.0; this flag
used to tell Uedit's display routines when not to update the display because
a menu was visible.  Uedit for the time being needs to be compatible with the
new and old Workbench, so the display routines have no way of knowing whether
you are looking at a menu or not; thus sometimes during an idle period a
display update occurs when you are examining a menu, and part of the menu is
chopped off by the display update.  This is cosmetic and harmless.))

(See Revision-History.)