From: Jean Louis <bugs@gnu.support>
To: martin rudalics <rudalics@gmx.at>
Cc: 60585@debbugs.gnu.org
Subject: bug#60585: 30.0.50; global-text-scale-adjust shrinks window (was not before)
Date: Mon, 9 Jan 2023 00:37:51 +0300 [thread overview]
Message-ID: <Y7s3r2qTYRW4x0ae@protected.localdomain> (raw)
In-Reply-To: <a6736c67-e59a-7623-6c28-23c1106eb40f@gmx.at>
* martin rudalics <rudalics@gmx.at> [2023-01-08 20:43]:
> > I have just pulled latest Emacs and used with -Q option:
> > `global-text-scale-adjust' which I have used last days upon first
> > startup.
> >
> > Before I have not observed that windows shrink by using `+' or `-'
> > within that command.
>
> I asked in another thread before and repeat the question here: Per se,
> 'global-text-scale-adjust' should never resize frames. You have to
> customize 'global-text-scale-adjust-resizes-frames' to achieve that
> effect. Please tell me what precisely you did. If you did not
> customize that option, something must be wrong within face-remap.el of
> which I'm not aware.
In emacs -Q it was tested and of course there is nothing customized.
I can't see it happening in Gtk build.
> > Configured using:
> > 'configure --with-x-toolkit=lucid --with-mailutils'
>
> I faintly recall that setting size hints with lucid here was completely
> broken a couple of years ago. In the attached patch I tried to excise
> some of the changes I made to fix that then. I also added some tracing
> information that should be dumped to a buffer called *foo*. So please
> try the patch and if it does not work (or things even get worse) post
> the contents of *foo* here.
I will try.
--
Jean
Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns
In support of Richard M. Stallman
https://stallmansupport.org/
next prev parent reply other threads:[~2023-01-08 21:37 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 [this message]
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
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
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=Y7s3r2qTYRW4x0ae@protected.localdomain \
--to=bugs@gnu.support \
--cc=60585@debbugs.gnu.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 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).