From: martin rudalics <rudalics@gmx.at>
To: Eli Barzilay <eli@barzilay.org>, Drew Adams <drew.adams@oracle.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
"21634@debbugs.gnu.org" <21634@debbugs.gnu.org>,
Juri Linkov <juri@linkov.net>
Subject: bug#21634: [External] : bug#21634: text-scale-adjust suggestion
Date: Tue, 7 Sep 2021 10:16:50 +0200 [thread overview]
Message-ID: <f42e158c-f08b-b6c3-65bb-3ec0e8d19ab2@gmx.at> (raw)
In-Reply-To: <CALO-guuis=6G91y=yGs-9TquAKHezuxgQR-nu=8kZ3s0XDqXRA@mail.gmail.com>
> With indent-rigidly this is even worse
> since the echo-area message disappears leaving you with no indication
> of it being active, which is essentially a mode which is extremely
> un-emacsy.
With `transient-mark-mode' the region stays highlighted until I'm done
with indenting. I would never look anywhere else for obtaining feedback
about a transient mode like the one triggered by `indent-rigidly'.
martin
next prev parent reply other threads:[~2021-09-07 8:16 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 [this message]
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=f42e158c-f08b-b6c3-65bb-3ec0e8d19ab2@gmx.at \
--to=rudalics@gmx.at \
--cc=21634@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).