unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jan Djärv" <jan.h.d@swipnet.se>
To: James Cloos <cloos@jhcloos.com>, 3784@emacsbugs.donarmstrong.com
Cc: emacs-pretest-bug@gnu.org
Subject: bug#3784: 23.1.50; Maximizing via the window manager does not survive changing	workspace
Date: Wed, 08 Jul 2009 16:35:46 +0200	[thread overview]
Message-ID: <4A54AEC2.10907@swipnet.se> (raw)
In-Reply-To: <m3skh74g5x.fsf@lugabout.jhcloos.org>

James Cloos skrev:
> Please write in English if possible, because the Emacs maintainers
> usually do not have translators to read other languages for them.
> 
> Your bug report will be posted to the emacs-pretest-bug@gnu.org mailing list.
> 
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug:
> 
> I use icewm.  I had been a while since my last compile; I suspect the
> recent commits dealing with splitting the h and v maximization are the
> cause of the behavioral change.
> 
> Now, when I use icewm’s maximize option to max emacs’s window (frame),
> switch to another workspace and then switch back, emacs resizes itself
> to its original geometry.  It appears to do so by loosing:
> 
> _NET_WM_STATE(ATOM) = _NET_WM_STATE_MAXIMIZED_VERT, _NET_WM_STATE_MAXIMIZED_HORZ
> 
> If I instead manually resize the window (frame) to fill the usable area —
> or any other size — said resizing remains.
> 
> AFAICT, only _NET_WM_STATE_MAXIMIZED_VERT and _NET_WM_STATE_MAXIMIZED_HORZ
> get lost on the switch back to the workspace containing emacs’ window.
> 

I can't reproduce this on icewm 1.2.37 on Ubuntu.
There was a bug on this erlier (3765 and 3766) that was fixed yesterday.  Can 
you try updating your CVS?

	Jan D.






      reply	other threads:[~2009-07-08 14:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-08 10:33 bug#3784: 23.1.50; Maximizing via the window manager does not survive changing workspace James Cloos
2009-07-08 14:35 ` Jan Djärv [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

  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=4A54AEC2.10907@swipnet.se \
    --to=jan.h.d@swipnet.se \
    --cc=3784@emacsbugs.donarmstrong.com \
    --cc=cloos@jhcloos.com \
    --cc=emacs-pretest-bug@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 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).