[5172] in Athena Bugs
rt 7.0F: xterm
daemon@ATHENA.MIT.EDU (cfields@ATHENA.MIT.EDU)
Wed Jun 13 21:09:31 1990
From: cfields@ATHENA.MIT.EDU
To: bugs@ATHENA.MIT.EDU
Date: Wed, 13 Jun 90 21:09:04 EDT
System name: entropy
Type and version: RTPC-ROMPC 7.0F (1 update(s) to same version)
Display type: apa16
What were you trying to do?
Trying to use xterm's border highlighting features.
If you are running uwm or no window manager, such that the application
gets to determine its own border width, xterm is supposed to highlight
and unhighlight its border depending on whether or not it has focus.
What's wrong:
They don't work. In fact, my cursory look indicates they don't even exist.
They do work, however, under the R3 version of xterm.
From the R3 source:
entropy 8:09pm 100> fgrep XSetWindowBorderPixmap *.c
Tekproc.c: XSetWindowBorderPixmap (screen->display, TShellWindow,
charproc.c: XSetWindowBorderPixmap (screen->display, VShellWindow,
From the R4 source:
entropy 8:29pm 139> fgrep XSetWindowBorderPixmap *.c
<nothing is printed>
I also saw no XtSetValues calls or anything else in relevant sections of
code where I looked to do this.
Excerpts from the manpage:
> keyboard input and terminal output. This is the window that
> contains the text cursor and whose border highlights when-
> ever the pointer is in either window. The active window can
> -ah This option indicates that xterm should always
> highlight the text cursor and borders. By default,
> xterm will display a hollow text cursor whenever the
> focus is lost or the pointer leaves the window.
> OTHER FEATURES
> Xterm automatically highlights the window border and text
> cursor when the pointer enters the window (selected) and
> unhighlights them when the pointer leaves the window
> (unselected). If the window is the focus window, then the
> window is highlighted no matter where the pointer is.
What should have happened:
One of the following:
(a.) xterm should be patched to implement/fix this feature.
(b.) references to this feature should be removed from the manpage.
i'm guessing that this was the intention, with the assumption
that it was expected window managers would now take on this
feature.
Please describe any relevant documentation references:
XTERM(1)
