Bug#241717: xterm: various colour problems (mouse cursor color, text colours)
On Fri, Apr 09, 2004 at 05:58:00AM -0400, Thomas Dickey <dickey@radix.net> wrote:
> of longstanding bugs. However, in the discussion so far, it is not clear
> whether you are referring to the text cursor or the mouse pointer.
Yes. I was refering to the mouse-cursor.
You have probably missed the remaining dialogue in the debian bug-report.
The maintainer kept replies off-list, and so I did the same.
The mails in the bug report detail the two problems quite thoroughly, so
if you ae interested in theese arguments you might want to read them.
> > If an app uses it as fg and this is bad, then I think that app has a
> > problem, not the terminal emulator, which, after all, just offers a fairly
> > standardized colour set.
>
> But it's not standardized.
Depends. It's standardized in some local standards, used in about all
existing implementations (see the bug report for a comparison between
terminal emulators on unix) and was documented for many years.
I would call that pretty much standardized. What you mean is probably
that there is no real standard the mandates that with force.
That is of course true. Neither the w3c nor the ietf nor... will care a
bit which exact colour is used in xterm or elsewhere :)
> > > I wonder if it shouldn't default to the VT100 widget's text foreground and
> > > background colors instead.
> > >
> > > What do you think?
> > >
> >
> > I tend to agree. That is (I think) how rxvt does it and (definitely) how
>
> I could revisit this issue. When I first looked at it (probably 1997),
> xterm was using Xt to lookup resource values automatically. Now it delays
> some of those til they're needed (so it would be possible to detect cases
> where a resource value was not set, and modify its default value dynamically).
Well, I would be fine with whoever changing the text fg/bg would also
need to adjust the mouse cursor colours, too, to get standard behaviour.
So the defaults in the binary and the debain appdefaults would need to
be corrected.
It's probably more user-friendly to make this automatically when unset,
but I am mainly concerned about default settings.
Changing the defaults is certainly the easiest fix for this very minor
problem.
--
-----==- |
----==-- _ |
---==---(_)__ __ ____ __ Marc Lehmann +--
--==---/ / _ \/ // /\ \/ / pcg@goof.com |e|
-=====/_/_//_/\_,_/ /_/\_\ XX11-RIPE --+
The choice of a GNU generation |
|
Reply to: