From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: salutis@me.com, gregory@heytings.org, 59122@debbugs.gnu.org
Subject: bug#59122: 29.0.50; global-text-scale-adjust not working
Date: Thu, 10 Nov 2022 09:56:01 +0200 [thread overview]
Message-ID: <83tu37s0oe.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmk0VMLKnFhCRj86ao2V5uAuDMCu6F9hf64WMjomP9bRrA@mail.gmail.com> (message from Stefan Kangas on Thu, 10 Nov 2022 01:44:18 +0100)
> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 10 Nov 2022 01:44:18 +0100
> Cc: Gregory Heytings <gregory@heytings.org>, 59122@debbugs.gnu.org, salutis@me.com
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > > Because text-scale-adjust is cruder: it uses a factor instead of an
> > > increment. The effect of global-text-scale-adjust is much smoother.
> >
> > This subtle difference should probably be in the doc string, as users
> > will normally assume that global-text-scale-adjust is just a
> > globalized version of text-scale-adjust.
>
> Is 'global-text-scale-adjust' new in Emacs 29? Maybe it would be
> better if they both work the same, presumably the same way as
> 'text-scale-adjust' does now (or the other way, if that's better).
> Then we could introduce a new defcustom to make them both behave the
> other way. Would that make sense?
Gregory says the different operation of the global mode is a feature,
so making them behave the same would either mean losing the feature or
an incompatible change to text-scale-adjust.
next prev parent reply other threads:[~2022-11-10 7:56 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-08 12:28 bug#59122: 29.0.50; global-text-scale-adjust not working Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-08 12:42 ` Eli Zaretskii
2022-11-08 12:47 ` Gregory Heytings
2022-11-08 21:48 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-09 3:33 ` Eli Zaretskii
2022-11-09 10:00 ` Gregory Heytings
2022-11-09 13:28 ` Stefan Kangas
2022-11-09 13:39 ` Gregory Heytings
2022-11-09 14:30 ` Stefan Kangas
2022-11-09 14:36 ` Robert Pluim
2022-11-09 14:43 ` Stefan Kangas
2022-11-09 14:48 ` Robert Pluim
2022-11-09 14:47 ` Gregory Heytings
2022-11-09 14:59 ` Stefan Kangas
2022-11-09 15:20 ` Robert Pluim
2022-11-09 14:36 ` Gregory Heytings
2022-11-09 14:51 ` Eli Zaretskii
2022-11-09 14:59 ` Eli Zaretskii
2022-11-09 15:25 ` Robert Pluim
2022-11-09 16:02 ` Gregory Heytings
2022-11-09 16:55 ` Eli Zaretskii
2022-11-10 0:44 ` Stefan Kangas
2022-11-10 7:56 ` Eli Zaretskii [this message]
2022-11-09 16:01 ` Gregory Heytings
2022-11-09 16:53 ` Eli Zaretskii
2022-11-09 16:18 ` Gregory Heytings
2022-11-10 0:26 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-10 8:33 ` Gregory Heytings
2022-11-10 16:16 ` Stefan Kangas
2022-11-10 17:00 ` Gregory Heytings
2022-11-11 16:05 ` Stefan Kangas
2022-11-13 0:23 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-13 3:05 ` Stefan Kangas
2022-11-13 6:59 ` Eli Zaretskii
2022-11-13 13:06 ` Stefan Kangas
2022-11-13 9:18 ` Gregory Heytings
2022-11-13 13:48 ` Stefan Kangas
2022-11-13 16:33 ` Eli Zaretskii
2022-11-13 19:39 ` Gregory Heytings
2022-11-13 20:09 ` Eli Zaretskii
2022-11-19 15:52 ` Gregory Heytings
2022-11-13 6:57 ` Eli Zaretskii
2022-11-13 9:10 ` Gregory Heytings
2022-11-13 22:37 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-14 0:00 ` Stephen Berman
2022-11-14 3:31 ` Eli Zaretskii
2022-11-09 13:40 ` Eli Zaretskii
2022-11-09 14:35 ` Stefan Kangas
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=83tu37s0oe.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=59122@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=salutis@me.com \
--cc=stefankangas@gmail.com \
/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).