all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Chong Yidong <cyd@gnu.org>
Cc: 12279@debbugs.gnu.org
Subject: bug#12279: 24.2.50; x-window-property always returns nil
Date: Sun, 26 Aug 2012 17:59:52 +0200	[thread overview]
Message-ID: <87lih1hcef.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <87bohx7odx.fsf@gnu.org> (Chong Yidong's message of "Sun, 26 Aug 2012 21:51:06 +0800")

Chong Yidong <cyd@gnu.org> writes:

>> Running GNU/Linux with Xorg, since some time I cannot get X window
>> properties anymore, that is, using emacs -Q (3 days old bzr
>> checkout), all of these return nil:
>>
>>   (x-window-property "WM_HINTS" nil "WM_HINTS" nil nil t)
>>   (x-window-property "WM_PROTOCOLS")
>>   (x-window-property "WM_NAME")
>>
>> I used xprop to get all X properies of the emacs frame itself, and I
>> can't get any of them using `x-window-property'.
>>
>> In GNU Emacs 24.2.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.4.4)
>>  of 2012-08-23 on thinkpad
>
> Can't really reproduce.  With latest trunk, also with a GTK 3 build
> (x86_64-unknown-linux-gnu, GTK+ Version 3.4.2), I get
>
> M-: (x-window-property "WM_HINTS" nil "WM_HINTS" nil nil t)
>   ==> [2 0 1 0 0 0 0 0 0]

I've updated my bzr checkout, and now it works again.  However, with the
slightly less recend emacs I'm currently running, I get nil.  This
was built on

,----[ C-h v emacs-build-time RET ]
| emacs-build-time is a variable defined in `version.el'.
| Its value is (20534 28456 614398 31000)
`----

which should be no more than 5 minutes later than the bzr update.
emacs-bzr-version is nil, so I cannot give the precise revision number.

Anyway, I'm happy it works again.

Bye,
Tassilo





      reply	other threads:[~2012-08-26 15:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-25 14:33 bug#12279: 24.2.50; x-window-property always returns nil Tassilo Horn
2012-08-26 13:51 ` Chong Yidong
2012-08-26 15:59   ` Tassilo Horn [this message]

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=87lih1hcef.fsf@thinkpad.tsdh.de \
    --to=tsdh@gnu.org \
    --cc=12279@debbugs.gnu.org \
    --cc=cyd@gnu.org \
    /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.