unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tyler Grinn <tylergrinn@gmail.com>
Cc: 57140@debbugs.gnu.org
Subject: bug#57140: New user option mouse-wheel-text-scale-buffer
Date: Thu, 11 Aug 2022 20:16:21 +0300	[thread overview]
Message-ID: <834jyipuoq.fsf@gnu.org> (raw)
In-Reply-To: <87a68asojm.fsf@gmail.com> (message from Tyler Grinn on Thu, 11 Aug 2022 13:00:45 -0400)

> From: Tyler Grinn <tylergrinn@gmail.com>
> Cc: 57140@debbugs.gnu.org
> Date: Thu, 11 Aug 2022 13:00:45 -0400
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> From: Tyler Grinn <tylergrinn@gmail.com>
> >> Cc: 57140@debbugs.gnu.org
> >> Date: Thu, 11 Aug 2022 11:23:51 -0400
> >> 
> >> Eli Zaretskii <eliz@gnu.org> writes:
> >> 
> >> > Thanks, but isn't it better to control the amount of scaling by
> >> > changing the value of text-scale-mode-step instead?  Having to scroll
> >> > the wheel several clicks without any effect would be confusing, I
> >> > think.  And text-scale-mode-step is already a user variable that is
> >> > available for this purpose.  So maybe you should try decreasing the
> >> > default value to, say, 1.02, to see if that satisfies your needs.
> >> 
> >> For some trackpads, controlling how many 'clicks' to scroll is quite
> >> difficult. The step size fixes the issue of scrolling too fast, but I
> >> still have trouble choosing the exact text scale I want. My preference
> >> is still for a larger step size and throttling scroll events.
> >
> > Sorry, I don't understand why you need to count clicks.  Typically
> > when users change the text scale, they just turn the wheel until the
> > size they get fits their needs.  Making text-scale-mode-step smaller
> > causes finer changes, so it's easier to be more precise in finding the
> > desired scale.
> >
> > Can you explain how your proposal makes it easier than that, and why?
> 
> Sure, let me rephrase: for two-finger scrolling, it's hard to emit a
> single scroll event. With a smaller step size it is easier to get it
> close to the scale I want, but regardless of the step size, choosing an
> exact text scale is difficult. This leads to buffers having slightly
> different text scales.

If that's the problem, shouldn't that be handled by techniques we use
in precision-scrolling?





  reply	other threads:[~2022-08-11 17:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-11 13:10 bug#57140: New user option mouse-wheel-text-scale-buffer Tyler Grinn
2022-08-11 13:20 ` Tyler Grinn
2022-08-11 13:28   ` Eli Zaretskii
2022-08-11 15:23     ` Tyler Grinn
2022-08-11 16:02       ` Eli Zaretskii
2022-08-11 17:00         ` Tyler Grinn
2022-08-11 17:16           ` Eli Zaretskii [this message]
2022-08-11 17:38             ` Tyler Grinn
2022-08-11 17:47               ` Eli Zaretskii
2022-08-11 19:24                 ` Tyler Grinn
2022-08-12  5:36                   ` Eli Zaretskii

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=834jyipuoq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=57140@debbugs.gnu.org \
    --cc=tylergrinn@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).