[1915] in Athena Bugs
nxsaber
daemon@ATHENA.MIT.EDU (jfc@ATHENA.MIT.EDU)
Thu Mar 16 06:50:15 1989
From: <jfc@ATHENA.MIT.EDU>
To: bugs@ATHENA.MIT.EDU
Date: Thu, 16 Mar 89 06:49:22 EST
I tried it on an RT display (with the program running on a vax), and saw
the same problem with the cursor: background/transparent sections are
interchanged.
After saber chokes on a file compiled with gcc -g ("Internal error..."),
its key bindings appear to be trashed. The only way to exit saber is to
kill it off in another window (there is no choice but to exit, since only
a handfull of keys do anything but beep).
Saber ignores the bell volume setting, and appears to use the maximum
volume at all times. Without a visual bell (or is there one that I
missed) this is unacceptable (i.e. it _will_ make me abandon this version
for long working sessions).
The menu buttons have round corners, but saber draws a rectangular shading
pattern onto them, with the result that the button background extends beyond
the corners of the buttons.
It is possible to scroll past the last line of text in a window. This should
not be allowed (a note on this: I was able to do it last night, but not now,
so I can't explain it too well. To repeat, drag on the scrollbar as if you
were moving to the end of file, and continue past the end).
As others have noticed, cut and paste does not behave in a useful manner.
Here is an excerpt from a session:
4 -> setopt load_flags -G
Warning #339: Incorrect redefinition of macro 'vax'.
The current definition is:
#define vax
5 -> setopt load_flags -G
6 ->
It is not clear why I got this error, or why it wasn't repeated.
Clicking "run" started the program with the contents of the X cut buffer
as arguments.
Text should be appended to the I/O window regardless of the currently
selected position. I selected "run" while scrolled back a few pages,
and it truncated the contents to that point.
Another Saber error:
Program exiting with return status = 0.
Resetting to top level.
29 -> Saber internal (parsing) error (signal 12, Bad system
(internal location 0x5b1be, 0x7fffe870)
Trying to recover...
Resetting to top level.
29 ->
By resizing the window, I was able to shrink the window at the right
which contains the buttons. It never returned to full size, even after
I enlarged the window again (so a number of buttons were permanently
gone). As before, this is running on an RT display.
Only the left mouse button activates buttons. (I assume this is because
the X toolkit is broken.)
A comment: judging by the appearance of the scroll bars, saber keeps too
much old data. This is a matter of opinion, but I'm concerned about
memory. Pressing ^T says it is using 3 Meg.
On the above error: bad system call. This appears to be caused by
"Dismiss"ing the "Saber Run" window.
--John Carr
