unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Barzilay <eli@barzilay.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 21634@debbugs.gnu.org
Subject: bug#21634: 24.5; Suggested improvement
Date: Thu, 22 Oct 2015 02:06:57 -0400	[thread overview]
Message-ID: <CALO-gutwXdOZB+ni5h-zD64dd2uSPfpFCSUsVh2uKaMiJF1ucA@mail.gmail.com> (raw)
In-Reply-To: <83d1wsxcuz.fsf@gnu.org>

On Tue, Oct 6, 2015 at 10:58 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: Eli Barzilay <eli@barzilay.org>
>> Date: Tue, 6 Oct 2015 08:04:03 -0400
>>
>> Would it make sense to implement `text-scale-adjust' as follows?  One
>> minor change is using the `keep-pred' argument to avoid re-setting
>> the map repeatedly, but the important change is having it timeout
>> after a few seconds.  This avoids the kind of mode-ish interaction
>> that feels weird in Emacs.
>
> FWIW, such modus operandi always annoys me.  Why should I be under
> pressure to do whatever is needed to prevent the setting from being
> reset?
>
> I don't really understand what's the problem with "mode-ish
> operation", feel free to elaborate.

Well, I suspect that I'm annoyed at the other direction: whenever I go
into the text-scaling mode, I try to remember to explicitly break it at
the end, so that I won't leave emacs in that state by mistake and be
surpries when I come back to it hours later (which actually happened to
me once, possibly putting me on this side of that fence).  OTOH, if the
delay is long enough, there is never any time pressure that I run into,
and it's easy to see when the timer kicked in by the echo area message
disappearing.


> If there's demand for resetting the size, I guess we could have it as
> optional behavior.

That's why I suggested the below extension to the meaning of the
`keep-pred` argument: specifying a timeout if it's a number.  Then there
could be a new global variable that specifies a default for that
argument, so with nil you get a single resize only (so you need to do
the full C-x C-= to resize further), with t you get the current
behavior, and with a number I get my timeout.

(I'm also suggesting it because I have a similarly "moded" function that
uses `set-transient-map' -- it seems like a good idea to me to specify a
default behavior for all such transient maps, so my function behaves in
the same way as text scaling.)


>> In fact, I find this useful in other cases too (a command that allows
>> you to resize the current window with the arrow keys), so I think that
>> it's useful to either add an additional timeout argument -- or perhaps
>> an extension where `keep-pred' can be a number of seconds and will do
>> the timeout thing.
>
> The user can always scale the size back when she wants, right?  Or am
> I missing something?

(Hopefully the above clarified it.  I'm talking about the resulting
interaction and how convenient it is, unrelated to being able to scale
things back.)

-- 
                    ((x=>x(x))(x=>x(x)))                   Eli Barzilay:
                    http://barzilay.org/                   Maze is Life!





  reply	other threads:[~2015-10-22  6:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-06 12:04 bug#21634: 24.5; Suggested improvement Eli Barzilay
2015-10-06 14:58 ` Eli Zaretskii
2015-10-22  6:06   ` Eli Barzilay [this message]
2015-10-23  8:24     ` Eli Zaretskii
2021-09-03 11:02     ` bug#21634: text-scale-adjust suggestion Lars Ingebrigtsen
2021-09-03 16:13       ` Juri Linkov
2021-09-04  6:54         ` Lars Ingebrigtsen
2021-09-05 16:40           ` Juri Linkov
2021-09-06  8:28             ` Lars Ingebrigtsen
2021-09-06 15:34               ` Juri Linkov
2021-09-06 22:15                 ` bug#21634: [External] : " Drew Adams
2021-09-06 22:31                   ` Eli Barzilay
2021-09-06 22:35                     ` Drew Adams
2021-09-07  8:16                     ` martin rudalics
2022-06-30 16:12           ` Juri Linkov
2022-07-01  9:17             ` Lars Ingebrigtsen
2022-07-01 15:40               ` Juri Linkov
2022-07-02 11:59                 ` Lars Ingebrigtsen
2022-07-03 16:36                   ` Juri Linkov
2022-07-04 10:51                     ` Lars Ingebrigtsen
2022-07-04 17:45                       ` Juri Linkov
2022-07-05 11:15                         ` Lars Ingebrigtsen
2022-07-05 13:21                           ` Robert Pluim
2022-07-05 16:38                             ` Lars Ingebrigtsen
2022-07-05 16:39                               ` Lars Ingebrigtsen
2022-07-06 17:42                             ` Juri Linkov
2022-07-07  8:01                               ` Lars Ingebrigtsen
2022-07-07 16:49                                 ` Juri Linkov
2022-07-07 18:04                                   ` Lars Ingebrigtsen

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=CALO-gutwXdOZB+ni5h-zD64dd2uSPfpFCSUsVh2uKaMiJF1ucA@mail.gmail.com \
    --to=eli@barzilay.org \
    --cc=21634@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).