unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: martin rudalics <rudalics@gmx.at>
To: Rolf Ade <rolf@pointsman.de>
Cc: 31650@debbugs.gnu.org
Subject: bug#31650: 26.1; Desktop mode adds wm stickiness to emacs windows.
Date: Wed, 30 May 2018 14:37:40 +0200	[thread overview]
Message-ID: <5B0E9B14.4040707@gmx.at> (raw)
In-Reply-To: <87wovle7ow.fsf@pointsman.de>

 > Now, this is interesting.

Unfortunately so.

 > I start emacs -Q. The frame comes up and isn't sticky.
 >
 > Now I evaluate your code from above in the scratch buffer. It returns
 > nil. _But_: It also puts the frame into sticky mode!

Does it also make the frame sticky when with emacs -Q you simply
evaluate

       (set-frame-parameter frame 'sticky nil)))

If so, then it would be helpful to debug x_set_sticky, set_wm_state,
x_send_client_event and x_fill_property_data to know which value gets
propagated there.  As it stands, it seems that we always turn on
stickyness when setting this frame parameter to nil, so somehow the
chain above seems to corrupt it.

Thanks, martin





  reply	other threads:[~2018-05-30 12:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30  1:12 bug#31650: 26.1; Desktop mode adds wm stickiness to emacs windows Rolf Ade
2018-05-30  6:40 ` martin rudalics
2018-05-30 10:53   ` Rolf Ade
2018-05-30 12:37     ` martin rudalics [this message]
2018-05-30 14:49       ` Rolf Ade
2018-05-31  7:28         ` martin rudalics
2018-05-31 13:00           ` Rolf Ade
2018-05-31 13:55             ` martin rudalics
2018-05-31 14:05               ` Robert Pluim
2018-05-31 16:02                 ` Robert Pluim
2018-06-01  6:09                   ` martin rudalics
2018-06-01  6:41                     ` Robert Pluim
2018-06-02  9:12                       ` martin rudalics
2018-06-04  9:14                         ` Robert Pluim
2018-05-31 22:58               ` Noam Postavsky
2018-06-01  6:09                 ` martin rudalics
2018-06-01 10:47             ` Rolf Ade
2018-06-02  9:13               ` martin rudalics

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5B0E9B14.4040707@gmx.at \
    --to=rudalics@gmx.at \
    --cc=31650@debbugs.gnu.org \
    --cc=rolf@pointsman.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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).