all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Howard Melman <hmelman@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
	55041@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#55041: 28.1; repeat-mode always prints message when enabled
Date: Tue, 21 Jun 2022 13:54:06 +0200	[thread overview]
Message-ID: <CADwFkmmjj9egVEpdvnB9r1wo6VbJG+1KVKL4w8ekbmza70SCww@mail.gmail.com> (raw)
In-Reply-To: <2E1D2C1A-5041-4BED-A82A-ACA00470B371@gmail.com>

Howard Melman <hmelman@gmail.com> writes:

> 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).

Right.  Using that config, I get the following *Messages* buffer after
starting Emacs:

  For information about GNU Emacs and the GNU system, type C-h C-a.
  Cleaning up the recentf list...done (0 removed)
  Repeat mode is enabled for 14 commands and 7 keymaps; see
‘describe-repeat-maps’.

Personally, I think we should remove both the recentf-mode and
repeat-mode messages here.  I don't find either of them very helpful
or interesting.





  reply	other threads:[~2022-06-21 11:54 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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CADwFkmmjj9egVEpdvnB9r1wo6VbJG+1KVKL4w8ekbmza70SCww@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=55041@debbugs.gnu.org \
    --cc=hmelman@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.