mirror of
https://github.com/IanDarwin/OpenLookCDROM.git
synced 2026-02-13 11:34:52 +00:00
92 lines
4.0 KiB
Plaintext
92 lines
4.0 KiB
Plaintext
# Gterm Bug List
|
|
# @(#)$Header: /it/grass/gterm/RCS/BUGS,v 1.6 1991/04/23 06:51:39 hugh Grass2 $
|
|
|
|
PSTerm was an experiment in general purpose terminal emulators. It
|
|
was a very interesting experiment, and taught us how to do a few
|
|
things. I feel that it has taught us how NOT to do many more things
|
|
in the NeWS environment, and that is has served as a good lesson.
|
|
|
|
We have made GTerm useful; it serves as a working
|
|
"emulator" of the psterm termcap. Further work on gterm seems
|
|
pointless, as more would be gained from a completely new terminal
|
|
program.
|
|
|
|
If you wish to hack on it, be warned that we have pushed it
|
|
beyond its design already, and that it may be hard going. We
|
|
will not be putting more effort into it except to fold in bug fixes
|
|
that are sent in to us (to "tech@toad.com").
|
|
|
|
Thanks to David Rosenthal for creating the original psterm;
|
|
it was a wondrous idea.
|
|
|
|
---
|
|
|
|
Window placement is in pixel units. This would perhaps best be fixed by a
|
|
parser for units on the command line, though currently NeWS does not
|
|
know the dimensions of its screen in inches or dots per inch. A
|
|
related problem is that although units are specified in points, the
|
|
resulting measurements are actually pixels.
|
|
|
|
Termcaps cannot describe how to emulate a terminal adequately. The
|
|
information in the termcap or terminfo files is not explicit enough to
|
|
let gterm emulate most terminals. Many termcap entries are written in
|
|
ways that depend on the inner workings of a terminal in such a way that
|
|
just looking at the termcap will not allow gterm to deal with a
|
|
program that knows more or different things about the emulated
|
|
terminal. An example is given in the README file. Terminfo is
|
|
somewhat better, but gterm does not use it. A proper job would
|
|
require more information than provided by both termcap and terminfo.
|
|
|
|
Display slowness. Sometimes when displaying a full screen of text,
|
|
psterm will display it in several chunks, with visible pauses between.
|
|
This may have to do with the default psio buffer size of 1K.
|
|
This turns out to be due mostly to the incredbly slow parser that
|
|
psterm/gterm uses to parse the character stream into possible termcap
|
|
functions. gterm now has custom parsers for dumb and psterm termcaps.
|
|
|
|
Some problems are in the fact that NeWS is young: on some servers, the
|
|
icon text gets cleared as soon as it is drawn because of a math 'off by
|
|
one' bug (edge condition) that is different for each machine. See
|
|
psterm.ps for new twiddle values to take care of this.
|
|
|
|
Sound (Control G, Beep) is not supported.
|
|
This is fixed servers that have the 'beep' command, OpenWindow and
|
|
MacNews 1.1.20.
|
|
|
|
Sometimes the input focus hilight is on but typing is ignored;
|
|
this is a LiteWindows (LiteUI) bug.
|
|
|
|
Fixed width fonts don't scale much of the time because there is
|
|
no font matrix information (fontname.fm files) for them.
|
|
|
|
There is a 64k limit to strings in NeWS 1.1, but due to typecheck bugs,
|
|
psterm.ps limits selections to 32k.
|
|
|
|
Some problems are just hard work, but it is not clear that psterm is
|
|
worth the extra effort to fix.
|
|
|
|
See the top each gterm?XXXX.psh file for problems/bugs with that toolkit
|
|
adaptor.
|
|
See the README file for more discussion of problems with the psterm concept.
|
|
|
|
-------------------
|
|
|
|
COMPATABILITY PROBLEMS:
|
|
|
|
All versions of gterm/psterm released by Grasshopper should not interfere
|
|
with the original Sun psterm.
|
|
|
|
The version of psterm released (on floppy disk) with MacNews 1.1.01 is
|
|
incompatable with patchlevel 0. Windows from these two releases
|
|
cannot be freely intermingled on a single screen.
|
|
All Version of from patchlevel 1 on should run on the same display
|
|
at the same time with no problems.
|
|
|
|
Patchlevel 1 (and all later releases) should not interfere with any
|
|
previous or later versions released by Grasshopper. HOWEVER, versions
|
|
beyond patchlevel 0 will not support patchlevel 0. The file psterm.ps
|
|
must be retained in order to run patchlevel 0 psterms. Patchlevel 1
|
|
does not contain a copy of psterm.ps. If you expect to encounter
|
|
patchlevel 0 psterms, make sure psterm.ps is installed in
|
|
/usr/NeWS/lib. This file is not provided after patchlevel 2.
|