From: Stefan Kangas <stefankangas@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: salutis@me.com, gregory@heytings.org, 59122@debbugs.gnu.org
Subject: bug#59122: 29.0.50; global-text-scale-adjust not working
Date: Wed, 9 Nov 2022 15:35:31 +0100 [thread overview]
Message-ID: <CADwFkmnTu3uBk4+rxBm+BCih_jQOU23-q+A_VfkMoL7UxQR1Qw@mail.gmail.com> (raw)
In-Reply-To: <83v8notfdi.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> Please step with Edebug into global-text-scale-adjust, and tell what
> do you see in the variable 'key' in the following fragment from the
> command:
>
> (let* ((key (event-basic-type last-command-event))
On the first invocation of 'global-text-scale-adjust':
last-command-event: 13 (#o15, #xd, ?\C-m)
key: 109 (#o155, #x6d, ?m)
When I then type '-', I see:
last-command-event: 45 (#o55, #x2d, ?-)
key: 45 (#o55, #x2d, ?-)
> (echo-keystrokes nil)
> (cur (face-attribute 'default :height))
> (inc
> (pcase key
> (?- (* (- increment) 5))
> (?0 (- global-text-scale-adjust--default-height cur))
> (_ (* increment 5))))
prev parent reply other threads:[~2022-11-09 14:35 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
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 [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=CADwFkmnTu3uBk4+rxBm+BCih_jQOU23-q+A_VfkMoL7UxQR1Qw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=59122@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=gregory@heytings.org \
--cc=salutis@me.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).