unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Howard Melman <hmelman@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 55041@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>,
	Stefan Kangas <stefan@marxist.se>
Subject: bug#55041: 28.1; repeat-mode always prints message when enabled
Date: Mon, 20 Jun 2022 18:04:42 -0400	[thread overview]
Message-ID: <2E1D2C1A-5041-4BED-A82A-ACA00470B371@gmail.com> (raw)
In-Reply-To: <86o7ynmgiy.fsf@mail.linkov.net>


> On Jun 20, 2022, at 12:51 PM, Juri Linkov <juri@linkov.net> wrote:
> 
>>>> 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 vote for keeping the message, but I have no strong opinion.
>> 
>> Why though?  How does it help me as a user?  And if I do need this
>> information for some reason, why can't I just flip the mode off and on
>> again?
> 
> Every minor mode displays a message, e.g.:
> 
>  M-x delete-selection-mode
>  Delete-Selection mode enabled
> 
>  M-x electric-pair-mode
>  Electric-Pair mode enabled

My original report was about enabling these in init.el and seeing the
message in the *Messages* buffer.  I have the following in my init:

(size-indication-mode)
(column-number-mode)
(show-paren-mode)
(recentf-mode)
(which-function-mode)
(global-hl-line-mode)
(context-menu-mode)			; new in Emacs 28
(global-so-long-mode)
(repeat-mode)				; new in Emacs 28

Of the above, only recentf-mode and repeat-mode write to the
*Messages* buffer on startup.  I added electric-pair-mode to my
init and it did not write to *Messages* though if I toggle it interactively
with M-x it does output (I assume to the echo area).

Howard





  reply	other threads:[~2022-06-20 22:04 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 [this message]
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=2E1D2C1A-5041-4BED-A82A-ACA00470B371@gmail.com \
    --to=hmelman@gmail.com \
    --cc=55041@debbugs.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).