From: Eli Zaretskii <eliz@gnu.org>
To: Eli Barzilay <eli@barzilay.org>
Cc: 21634@debbugs.gnu.org
Subject: bug#21634: 24.5; Suggested improvement
Date: Tue, 06 Oct 2015 17:58:44 +0300 [thread overview]
Message-ID: <83d1wsxcuz.fsf@gnu.org> (raw)
In-Reply-To: <22035.47283.76000.848103@gargle.gargle.HOWL>
> 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.
If there's demand for resetting the size, I guess we could have it as
optional behavior.
> 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?
next prev parent reply other threads:[~2015-10-06 14:58 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 [this message]
2015-10-22 6:06 ` Eli Barzilay
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=83d1wsxcuz.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21634@debbugs.gnu.org \
--cc=eli@barzilay.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).