Re: (window-system) returns nil on after-make-frame-functions when creating an X frame

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

Mike Mattie <codermattie@gmail.com> writes:

  > Hi,
  > 
  > The behavior of (window-system) as it stands has a corner-case that
  > does not make sense.
  > 
  > I run a function on after-make-frame-functions that loads my GUI configuration
  > (previously discussed).
  > 
  > To make sure it runs only when a X frame is created, vs. a TTY I would check
  > that it is an X frame.
  > 
  > To do this I called (window-system) which normally returns "x". It is not
  > the best idea, but intuitively after the X frame is created it would sensibly
  > return "x".
  > 
  > Currently it returns nil. When (window-system) is evaluated in the scratch
  > buffer sometime after the frame is made, well after after-make-frame-functions
  > it does indeed return "x".

How are you calling (window-system) ? You should be calling it from
within a `with-selected-frame'