From: Stefan Kangas <stefankangas@gmail.com>
To: "Rudolf Adamkovič" <salutis@me.com>
Cc: Gregory Heytings <gregory@heytings.org>, 59122@debbugs.gnu.org
Subject: bug#59122: 29.0.50; global-text-scale-adjust not working
Date: Sun, 13 Nov 2022 04:05:56 +0100 [thread overview]
Message-ID: <CADwFkm=syR4N6jX0erngtsPbD=Jb6jrS9vr1Qbbjepa9swn90g@mail.gmail.com> (raw)
In-Reply-To: <m2iljju2g1.fsf@me.com>
Rudolf Adamkovič <salutis@me.com> writes:
> Works here too, but the function still increases the font size right
> after I execute it.
>
> In other words, to have *no change* in font size, I have do:
>
> 1. type `M-x' and `global-text-scale-adjust' and `RET'
> 2. type `-'
> 3. type `q'
>
> `text-scale-adjust' does this too, so I guess ... a feature?
I guess the idea is that you should invoke it with `C-x C-M-0'? But
that seems to have another problem with the patch - when I type it I
get:
Debugger entered--Lisp error: (error "Lisp nesting exceeds
‘max-lisp-eval-depth’")
redisplay--unhighlight-overlay-function(nil)
redisplay--update-region-highlight(#<window 3 on *scratch*>)
run-hook-with-args(redisplay--update-region-highlight #<window 3 on
*scratch*>)
redisplay--pre-redisplay-functions(nil)
redisplay_internal\ \(C\ function\)()
redisplay(force)
global-text-scale-adjust(1)
[[[... 1590 identical lines elided /SK ...]]
global-text-scale-adjust(1)
funcall-interactively(global-text-scale-adjust 1)
call-interactively(global-text-scale-adjust nil nil)
command-execute(global-text-scale-adjust)
> Also, the two function now scale super-duper differently. :-/
Do you mean 'text-scale-adjust' and 'global-text-scale-adjust'? I see
the same here.
next prev parent reply other threads:[~2022-11-13 3:05 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 [this message]
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='CADwFkm=syR4N6jX0erngtsPbD=Jb6jrS9vr1Qbbjepa9swn90g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=59122@debbugs.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).