From: Juri Linkov <juri@linkov.net>
To: "Kévin Le Gouguec" <kevin.legouguec@gmail.com>
Cc: Dmitry Gutov <dgutov@yandex.ru>,
Ramesh Nedunchezian <rameshnedunchezian@outlook.com>,
47566@debbugs.gnu.org
Subject: bug#47566: 28.0.50; diff-hl should use `repeat-mode' ... and not `smartrep'
Date: Wed, 14 Apr 2021 21:10:12 +0300 [thread overview]
Message-ID: <87h7k8n3uy.fsf@mail.linkov.net> (raw)
In-Reply-To: <TY2PR0101MB36932D978661080B581457C6DA7A9@TY2PR0101MB3693.apcprd01.prod.exchangelabs.com>
>> Consider adding a repeat-mode-echo option which follows what Smartrep
>> does: instead of adding to the echo area, it just highlights the
>> changed state in the mode line (basically a long mode lighter saying
>> "========SMARTREP=======") and also colors the mode-line green.
>>
>> IME that works well as an indicator that we're in a "special" state.
>>
>> Though perhaps we could use a smaller text (like "[REPEAT]") and only
>> color the text inside the brackets, rather than the whole
>> mode-line. Could use some experimentation.
>
> An entry in mode-line-modes, à la compilation-in-progress, would be
> lovely IMO.
compilation-in-progress is a good example of an unobtrusive indicator
in the mode line. Now added to repeat-mode.
PS: like your message-subject-re-regexp turned the subject into
"Re: peat lambda" on emacs-devel, it removed the bug number
from the subject here :)
next prev parent reply other threads:[~2021-04-14 18:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-02 5:40 bug#47566: 28.0.50; diff-hl should use `repeat-mode' ... and not `smartrep' Ramesh Nedunchezian
2021-04-03 22:08 ` Dmitry Gutov
2021-04-05 20:43 ` Juri Linkov
2021-04-06 22:44 ` Dmitry Gutov
2021-04-08 18:57 ` Juri Linkov
2021-04-10 1:40 ` Dmitry Gutov
2021-04-10 8:38 ` Ramesh Nedunchezian
2021-04-10 22:59 ` Juri Linkov
2021-04-11 6:48 ` Ramesh Nedunchezian
2021-04-11 22:51 ` Juri Linkov
2021-04-12 16:16 ` Juri Linkov
2021-04-10 22:58 ` Juri Linkov
2021-04-10 23:27 ` Dmitry Gutov
2021-04-12 16:17 ` Juri Linkov
2021-04-13 23:54 ` Dmitry Gutov
2021-04-14 7:14 ` Kévin Le Gouguec
2021-04-14 18:10 ` Juri Linkov [this message]
2021-04-14 19:12 ` Kévin Le Gouguec
2021-04-14 19:52 ` Juri Linkov
2021-04-14 20:21 ` Juri Linkov
2021-04-14 20:48 ` Kévin Le Gouguec
2021-04-14 21:58 ` Juri Linkov
2021-04-14 23:35 ` Dmitry Gutov
2021-11-14 20:25 ` Juri Linkov
2021-11-15 5:26 ` Lars Ingebrigtsen
2021-11-15 17:40 ` Juri Linkov
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=87h7k8n3uy.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=47566@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=kevin.legouguec@gmail.com \
--cc=rameshnedunchezian@outlook.com \
/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).