Okay. What about making it work when specifying a frame, and building with a toolkit? It seems there is an outer-window-id (which is the top-level window as far as the window manager and other X programs like xprop are concerned), and then there is window-id.

While I see now that this can be worked around in elisp, shouldn't x-window-property use outer-window-id when a frame is specified, since that is almost certainly what is desired?

On Wed, May 21, 2014 at 12:27 AM, Andreas Schwab <schwab@suse.de> wrote:

Jeremy Maitin-Shepard <jeremy@jeremyms.com> writes:

> x-window-property seems to return nil for most properties.
>
> (x-window-property "WM_HINTS") -> returns non-nil
>
> (x-window-property "WM_NAME") -> returns nil even though the property is
> set (and displayed by xprop)
>
> (x-window-property "_NET_WM_STATE") -> returns nil even though property is
> set
>
> In fact I haven't found any property I can read other than WM_HINTS.

You can, if you use the same window id for the target window as xprop
(or build emacs without toolkit).

Andreas.

--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."