From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Barzilay <eli@barzilay.org>,
"21634@debbugs.gnu.org" <21634@debbugs.gnu.org>
Subject: bug#21634: [External] : bug#21634: text-scale-adjust suggestion
Date: Mon, 6 Sep 2021 22:15:34 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488DEB83233F5557B33170EF3D29@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87eea1hhzc.fsf@mail.linkov.net>
> Another command that could use it as well is 'indent-rigidly'.
> Currently it's too inconvenient to type C-g to get out of it.
> Exiting after a delay would be a better option.
Not that I care much about this particular fiddling,
but IMHO, `C-g' to "get out of" what is essentially
a modal, or near-modal interaction, is emacsy and
makes perfect sense. Having a time-out "get out of"
such contexts seems to me quite wrong & unfriendly.
(Again though, not much concern on my part, for
quitting this command's repeating behavior.)
Timers do things silently, at moments users are
often not aware of. And users certainly don't want
to _wait_ for a timer as the way to initiate or
terminate some action. At a minimum there should
be a way to quit on demand (i.e. do it now!).
next prev parent reply other threads:[~2021-09-06 22:15 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 ` Drew Adams [this message]
2021-09-06 22:31 ` bug#21634: [External] : " 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=SJ0PR10MB5488DEB83233F5557B33170EF3D29@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=21634@debbugs.gnu.org \
--cc=eli@barzilay.org \
--cc=juri@linkov.net \
--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).