From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Barzilay <eli@barzilay.org>, 21634@debbugs.gnu.org
Subject: bug#21634: text-scale-adjust suggestion
Date: Fri, 03 Sep 2021 19:13:45 +0300 [thread overview]
Message-ID: <871r65ab7q.fsf@mail.linkov.net> (raw)
In-Reply-To: <87zgstyl9e.fsf_-_@gnus.org> (Lars Ingebrigtsen's message of "Fri, 03 Sep 2021 13:02:53 +0200")
>> 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.
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> We now have something similar in the form of `repeat-exit-timeout'
> (which defaults to "no timeout"). Perhaps it would make sense to use
> this in `text-scale-adjust'? Any opinions?
Indeed, text-scale-adjust could be trivially modified to use
repeat-map that supports repeat-exit-timeout. But the problem is
that this feature is available only when repeat-mode is enabled.
Maybe not a problem to enable it when the user wants repeatable keys.
next prev parent reply other threads:[~2021-09-03 16:13 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
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 [this message]
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=871r65ab7q.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=21634@debbugs.gnu.org \
--cc=eli@barzilay.org \
--cc=larsi@gnus.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).