unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "62275@debbugs.gnu.org" <62275@debbugs.gnu.org>
Subject: bug#62275: 28.2; Changing major mode changes the current text scaling
Date: Sun, 19 Mar 2023 17:22:39 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488CC3A7980A2C1B166AA71F3839@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <83bkkoadt1.fsf@gnu.org>

> > I tried doing this, but it didn't fix the behavior.
> >
> > (put 'text-scale-mode-remapping 'permanent-local t)
> > (put 'text-scale-mode-lighter 'permanent-local t)
> > (put 'text-scale-mode-amount 'permanent-local t)
> 
> You need to do this with face-remapping-alist.

The request is not about _setting_ the remapping of any face or set of faces.

The request is for the effect of text-scaling, from _interactive_ use of `text-scale-adjust', to not be removed when the major mode is changed and the buffer isn't switched.

IOW, same buffer: keep its current scaling regardless of (only) major-mode changes.

> > If there's (also) a good use case for the current behavior then maybe we
> > could have a user option, to choose whether a major-mode change resets
> > the text scale?
> 
> Sounds like creeping featurism to me.  If you want the text size
> larger, then why not customize the default face, and have that done
> once and for all?  Text-scale is by definition a temporary measure.

I don't want the text size larger in general or by default - of any face, let alone face `default'.

It's about interactive use of `text-scale-adjust`.  Seems to me its behavior should be only buffer-specific and not affected by a major-mode change.  Is that not a reasonable behavior to want, if not even generally _expect_?





  reply	other threads:[~2023-03-19 17:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-19 16:03 bug#62275: 28.2; Changing major mode changes the current text scaling Drew Adams
2023-03-19 16:47 ` Eli Zaretskii
2023-03-19 17:22   ` Drew Adams [this message]
2023-03-19 17:40     ` Eli Zaretskii
2023-03-19 21:50       ` Drew Adams
2023-03-20 11:58         ` Eli Zaretskii
2023-03-20 16:19           ` Drew Adams
2023-03-20 17:00             ` Eli Zaretskii
2023-03-20 17:24               ` Drew Adams

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=SJ0PR10MB5488CC3A7980A2C1B166AA71F3839@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=62275@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).