Re: colours in client on xterm (if an X frame is open at same time)

[Dan Nicolaescu <dann@ics.uci.edu>]

Ulrich Mueller <ulm@gentoo.org> writes:

  > >>>>> On Thu, 7 Jan 2010, Dan Nicolaescu wrote:
  > 
  > >> Anyway, my point was, why are the colours _different_ in the second
  > >> case? Especially, why is the background grey?
  > 
  > > It should not be.   I can't reproduce it here, but by emacs is about
  > > 2 weeks old.
  > 
  > > In the grey case, do you get something odd if you do a describe-face
  > > for the default face?
  > 
  > Differences between normal and grey case are:
  > 
  >    -    Foreground: unspecified-fg
  >    -    Background: unspecified-bg
  >    +    Foreground: black
  >    +    Background: white
  > 
  >    -          Font: unspecified
  >    -       Fontset: nil
  >    +          Font: #<font-spec nil nil nil nil nil nil nil nil nil nil nil nil ((user-spec . monospace-12))>
  >    +       Fontset: -unknown-DejaVu Sans Mono-normal-normal-normal-*-13-*-*-*-m-0-fontset-startup
  > 
  > > Is this something new? Do you get the same behavior with 23.1?
  > > If not, then doing a binary search for the patch that broke it is your
  > > best bet...
  > 
  > I had hoped that the bisecting could be avoided, but here we go.
  > 
  > The "grey background" started with revision 99013 (and reverting this
  > changeset in the trunk of today brings back the old behaviour):
  > 
  >    revno: 99013
  >    committer: Dan Nicolaescu <dann@ics.uci.edu>
  >    branch nick: trunk
  >    timestamp: Mon 2009-12-07 06:30:30 +0000
  >    message:
  >      Get the background mode from the terminal for xterm, and set
  >      faces accordingly.
  >      * term/xterm.el (xterm-set-background-mode): New function.
  >      (terminal-init-xterm): Use it in case xterm supports background
  >      color queries.  Recompute faces after getting the background
  >      color.

Thanks.

In your case the only effect that patch should have is to move the call
 (tty-set-up-initial-frame-faces) from before

(let ((coding-system-for-read 'binary)

to after it.

What happens in that `let' should not matter to your setup because your
background is light, so change 99013 should be a no-op in your case.

Hmmm, this is very odd...