From: Howard Melman <hmelman@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 55041@debbugs.gnu.org
Subject: bug#55041: 28.1; repeat-mode always prints message when enabled
Date: Wed, 20 Apr 2022 14:32:58 -0400 [thread overview]
Message-ID: <E5110317-B55A-432E-90B9-31199FE1B896@gmail.com> (raw)
In-Reply-To: <865yn3adfv.fsf@mail.linkov.net>
On Apr 20, 2022, at 1:10 PM, Juri Linkov <juri@linkov.net> wrote:
>
>> Minor thing: When repeat-mode is enabled it calls message with:
>>
>> "Repeat mode is enabled for %d commands and %d keymaps; see `describe-repeat-maps'."
>>
>> I'm working on my configuration and of all the other minor-modes
>> I enable by calling from lisp, none of them print such a message,
>> so this stands out when I'm looking at *Messages*.
>
> This is exactly the reason why it outputs its statistics to *Messages*,
> so you could see how many commands are affected by this mode.
> Also I see that it doesn't stand out too much,
> for example, I have after starting Emacs in *Messages*:
>
> Starting new Ispell process /usr/bin/hunspell with american dictionary...done
> Repeat mode is enabled for 23 commands and 9 keymaps; see ‘describe-repeat-maps’.
> Cleaning up the recentf list...done (0 removed)
> Desktop: 1 frame, 19 buffers restored.
>
> But if the majority will prefer to remove it, then I could commit such a patch.
> So we need just one additional vote that supports this change :)
I also found that recentf does something similar. So if a few things give these
informational messages (particularly to *Messages*) then I have no complaints.
Seeing just the one I thought it might be violating a convention. Feel free to
close this.
Howard
next prev parent reply other threads:[~2022-04-20 18:32 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 [this message]
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
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=E5110317-B55A-432E-90B9-31199FE1B896@gmail.com \
--to=hmelman@gmail.com \
--cc=55041@debbugs.gnu.org \
--cc=juri@linkov.net \
/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).