From: Howard Melman <hmelman@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: stefan@marxist.se, larsi@gnus.org, 55041@debbugs.gnu.org,
juri@linkov.net
Subject: bug#55041: 28.1; repeat-mode always prints message when enabled
Date: Wed, 22 Jun 2022 10:30:42 -0400 [thread overview]
Message-ID: <B6FEE777-5FE0-4A0D-8E89-A588EBEC286D@gmail.com> (raw)
In-Reply-To: <83bkukkepg.fsf@gnu.org>
On Jun 22, 2022, at 9:30 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>> I could inhibit messages for those two but it seems a little messy.
>
> Please don't: those messages are both informative and important.
The context was in my own config.
Could you explain why you find them important? Why is it important
that I know recent is trimming some items when it reaches its max
limit? That's just normal behavior.
Why is it important I know how many commands repeat-mode affects?
Other minor-modes (like cua-mode) don't tell me or log how many
bindings they provide. And the "see describe-repeat-maps" point is in
the command's docstring which is the most natural place for it.
Both of these strike me as useful only when debugging.
To sum up so far:
Juri> This is exactly the reason why it outputs its statistics to *Messages*,
Juri> But if the majority will prefer to remove it, then I could
Juri> commit such a patch. So we need just one additional vote that
Juri> supports this change :)
Howard> I also found that recentf does something similar. So if a few
Howard> things give these informational messages (particularly to
Howard> *Messages*) then I have no complaints. Seeing just the one I
Howard> thought it might be violating a convention. Feel free to
Howard> close this.
But clearly I don't find these message useful :)
Lars> I vote for keeping the message, but I have no strong opinion.
Lars> I can't remember what my reasoning was back then, and looking at
Lars> it again, I agree with you -- it doesn't really seem very useful
Lars> to a user.
StefanK> Personally, I think we should remove both the recentf-mode
StefanK> and repeat-mode messages here. I don't find either of them
StefanK> very helpful or interesting.
Eli> Please don't: those messages are both informative and important.
Howard
next prev parent reply other threads:[~2022-06-22 14:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 14:53 bug#55041: 28.1; repeat-mode always prints message when enabled Howard Melman
2022-04-20 17:10 ` Juri Linkov
2022-04-20 18:32 ` Howard Melman
2022-04-21 11:55 ` Lars Ingebrigtsen
2022-06-19 14:09 ` Stefan Kangas
2022-06-19 14:22 ` Lars Ingebrigtsen
2022-06-20 16:51 ` Juri Linkov
2022-06-20 22:04 ` Howard Melman
2022-06-21 11:54 ` Stefan Kangas
2022-06-21 17:49 ` Juri Linkov
2022-06-21 18:42 ` Drew Adams
2022-06-21 20:54 ` Howard Melman
2022-06-22 7:33 ` Juri Linkov
2022-06-22 13:16 ` Howard Melman
2022-06-22 13:30 ` Eli Zaretskii
2022-06-22 14:30 ` Howard Melman [this message]
2022-06-22 15:34 ` Drew Adams
2022-06-22 16:00 ` Eli Zaretskii
2022-06-22 16:18 ` Howard Melman
2022-06-22 16:22 ` Eli Zaretskii
2022-06-23 9:01 ` Lars Ingebrigtsen
2022-06-23 9:54 ` Eli Zaretskii
2022-06-23 11:36 ` Lars Ingebrigtsen
2022-06-23 12:58 ` Eli Zaretskii
2022-06-22 18:30 ` Juri Linkov
2022-06-22 19:29 ` Howard Melman
2022-06-21 23:16 ` Stefan Kangas
2022-06-21 17:46 ` 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=B6FEE777-5FE0-4A0D-8E89-A588EBEC286D@gmail.com \
--to=hmelman@gmail.com \
--cc=55041@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=stefan@marxist.se \
/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).