From: Jeremy Maitin-Shepard <jeremy@jeremyms.com>
To: Andreas Schwab <schwab@suse.de>
Cc: 17537@debbugs.gnu.org
Subject: bug#17537: x-window-property doesn't work for most properties
Date: Wed, 21 May 2014 00:57:28 -0700 [thread overview]
Message-ID: <CAKJfoCEvueQRrQYUjeWdB1Q=k=71WHYJk60RSxfmbft5Q5Cw_A@mail.gmail.com> (raw)
In-Reply-To: <mvmha4jpp5d.fsf@hawking.suse.de>
[-- Attachment #1: Type: text/plain, Size: 1280 bytes --]
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."
>
[-- Attachment #2: Type: text/html, Size: 1916 bytes --]
next prev parent reply other threads:[~2014-05-21 7:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-21 1:12 bug#17537: x-window-property doesn't work for most properties Jeremy Maitin-Shepard
2014-05-21 7:27 ` Andreas Schwab
2014-05-21 7:57 ` Jeremy Maitin-Shepard [this message]
2014-05-21 15:42 ` Jan Djärv
2014-05-24 8:42 ` Jan Djärv
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAKJfoCEvueQRrQYUjeWdB1Q=k=71WHYJk60RSxfmbft5Q5Cw_A@mail.gmail.com' \
--to=jeremy@jeremyms.com \
--cc=17537@debbugs.gnu.org \
--cc=schwab@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.