all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: Gregory Heytings <gregory@heytings.org>
Cc: martin rudalics <rudalics@gmx.at>, 60585@debbugs.gnu.org
Subject: bug#60585: 30.0.50; global-text-scale-adjust shrinks window (was not before)
Date: Mon, 9 Jan 2023 15:44:12 +0300	[thread overview]
Message-ID: <Y7wMHNAIMWTWZ/Cl@protected.localdomain> (raw)
In-Reply-To: <3f4b5c597227e1c31900@heytings.org>

Let me just remind you that it is considered application (Emacs) error
by IceWm developer.

See:
https://github.com/ice-wm/icewm/issues/115

Where gijsbers said, that:

> IceWM historically has ignored the USSize field in the
> WM_NORMAL_HINTS property. To enforce a size an app must set both the
> PMinSize and the PMaxSize to the same value. Because there is no
> PMaxSize, icewm is free to adjust the size to a value which is in
> accordance to the emacs provided PBaseSize and PResizeInc. See the
> ICCCM for details. IceWM is still standards conformant. It just has
> a different interpretation than other WMs.

And then here is the reference:
https://x.org/releases/X11R7.6/doc/xorg-docs/specs/ICCCM/icccm.html

Search for: "PMaxSize" and review if there is something that Emacs
could or should do.

While in meantime IceWM developer provided tolerance patch:
https://github.com/bbidulock/icewm/commit/cb144a07ce0b948177030a2f56b83fc07d2b2a44

-- 
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/





  parent reply	other threads:[~2023-01-09 12:44 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-05 22:28 bug#60585: 30.0.50; global-text-scale-adjust shrinks window (was not before) Jean Louis
2023-01-06  6:50 ` Eli Zaretskii
2023-01-06  8:17   ` Gregory Heytings
2023-01-06  8:41     ` Gregory Heytings
2023-01-06 13:01       ` Jean Louis
2023-01-06 13:26         ` Gregory Heytings
2023-01-06 14:03           ` Gregory Heytings
2023-01-06 15:16             ` Gregory Heytings
2023-01-06 16:32             ` Jean Louis
2023-01-06 22:05               ` Gregory Heytings
2023-01-06 22:24                 ` Jean Louis
2023-01-07  2:05                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-07 17:24                     ` Jean Louis
2023-01-06 22:25                 ` Jean Louis
2023-01-06 22:35                   ` Gregory Heytings
2023-01-07  9:36                     ` Gregory Heytings
2023-01-08  0:38                       ` Jean Louis
2023-01-08 21:41                         ` Gregory Heytings
2023-01-06 14:05           ` Eli Zaretskii
2023-01-06 22:21             ` Jean Louis
2023-01-06 16:35           ` Jean Louis
2023-01-06 12:57     ` Jean Louis
2023-01-06 12:55   ` Jean Louis
2023-01-06 13:18     ` Eli Zaretskii
2023-01-06 16:27       ` Jean Louis
2023-01-06 16:50         ` Eli Zaretskii
2023-01-08 17:42 ` martin rudalics
2023-01-08 21:37   ` Jean Louis
2023-01-09 10:07     ` martin rudalics
2023-01-08 22:14   ` Gregory Heytings
2023-01-09 10:09     ` martin rudalics
2023-01-09 18:00       ` martin rudalics
2023-01-09 12:44     ` Jean Louis [this message]
2023-01-13  6:35   ` Jean Louis
2023-01-13  6:43   ` Jean Louis
2023-01-13  8:38     ` martin rudalics
2023-01-13 17:38       ` Jean Louis
2023-01-14 10:24         ` 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

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

  git send-email \
    --in-reply-to=Y7wMHNAIMWTWZ/Cl@protected.localdomain \
    --to=bugs@gnu.support \
    --cc=60585@debbugs.gnu.org \
    --cc=gregory@heytings.org \
    --cc=rudalics@gmx.at \
    /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.