From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Barzilay <eli@barzilay.org>, Eli Zaretskii <eliz@gnu.org>,
21634@debbugs.gnu.org
Subject: bug#21634: text-scale-adjust suggestion
Date: Fri, 01 Jul 2022 18:40:37 +0300 [thread overview]
Message-ID: <86k08wzx5e.fsf@mail.linkov.net> (raw)
In-Reply-To: <878rpdyyxo.fsf@gnus.org> (Lars Ingebrigtsen's message of "Fri, 01 Jul 2022 11:17:23 +0200")
>> We don't need post-command-hook here - this leaves us with just
>> set-transient-map. As was already suggested, we need either
>> to add a new optional arg TIMEOUT to set-transient-map,
>> or allow a number of seconds in the existing arg KEEP-PRED.
>>
>> Then another question is how the users could customize the timeout.
>> One variable to customize timeout for all commands that use
>> set-transient-map? Or separate variables for every command:
>> one for indent-rigidly, one for text-scale-adjust?
>
> I think one variable for the timeout would be sufficient, and a value of
> (say) `timeout' for KEEP-PRED could instruct set-transient-map to use
> that timeout, perhaps?
Actually, I can imagine when someone might want to keep a transient map
active with KEEP-PRED, but still deactivate it after a timeout. So
a separate TIMEOUT looks cleaner.
Anyway, repeat-mode has separate options for repeat-exit-timeout
and constructs a message, so I could copy the same code from repeat-mode
to set-transient-map.
next prev parent reply other threads:[~2022-07-01 15:40 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
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 [this message]
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=86k08wzx5e.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=21634@debbugs.gnu.org \
--cc=eli@barzilay.org \
--cc=eliz@gnu.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).