bug#62275: 28.2; Changing major mode changes the current text scaling

[Eli Zaretskii <eliz@gnu.org>]

> From: Drew Adams <drew.adams@oracle.com>
> CC: "62275@debbugs.gnu.org" <62275@debbugs.gnu.org>
> Date: Sun, 19 Mar 2023 21:50:29 +0000
> 
> > But that's what text-scaling does: it enlarges
> > the default face's font.
> 
> You seem to be dancing around this.

Why the sarcasm/insult?  I don't have to have this conversation, and I
certainly won't if you keep this attitude.

> Text-scaling does NOT "customize the default face".

Of course, it does.

> What's more, actually changing the font of face
> `default' is the same as changing frame property
> `font'.

Yes, and that's equivalent to what text-scaling does.

> And doing that changes the text size for ALL
> windows in the frame - whatever buffers they
> show, not just a single buffer.

Yes, as expected.  Text-scaling, by contrast, is a buffer-local
behavior, and buffer-local behaviors get reset when the major mode
changes.

So we have no made the full circle.

> These are different things: (1) zooming a buffer
> (everywhere) and (2) zooming a frame (all its
> windows, whatever the buffers) and zooming
> nothing in any other frame.

Not very different, since we now have global-text-scale-adjust and
friends.

> AFAICT, what you said here repeats what I said:
> 
>   changing the major mode kills all local variables
> 
> and:
> 
>   the text-scale ... is a buffer-local behavior,
>   and modes have no memory of what that scaling was.
> 
> I pointed out those things at the outset.
> 
> I was thinking that making those 3 buffer-local
> variables permanently buffer-local would provide
> that missing memory.  But it seems that making
> `face-remapping-alist' permanently local does
> just what I want.

Yes.  As I pointed out at the outset.