From: Drew Adams <drew.adams@oracle.com>
To: Howard Melman <hmelman@gmail.com>, Eli Zaretskii <eliz@gnu.org>
Cc: "55041@debbugs.gnu.org" <55041@debbugs.gnu.org>,
"larsi@gnus.org" <larsi@gnus.org>,
"stefan@marxist.se" <stefan@marxist.se>,
"juri@linkov.net" <juri@linkov.net>
Subject: bug#55041: 28.1; repeat-mode always prints message when enabled
Date: Wed, 22 Jun 2022 15:34:07 +0000 [thread overview]
Message-ID: <SJ0PR10MB5488567ECA5B8312259E5A79F3B29@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <B6FEE777-5FE0-4A0D-8E89-A588EBEC286D@gmail.com>
> >> I could inhibit messages for those two but it seems a little messy.
> > Please don't: those messages are both informative and important.
>
> Howard> ...Could you explain why you find them important?...
> Howard> To sum up so far:
> Juri> This is exactly the reason why it outputs its statistics to
> *Messages*,
> Lars> I vote for keeping the message, but I have no strong opinion.
> Lars> ...looking at it again...it doesn't really seem very useful
> Lars> to a user.
> StefanK> ... we should remove both the recentf-mode
> StefanK> and repeat-mode messages here...
> Eli> Please don't: those messages are both informative and important.
1. *Messages* should record _all_ echo-area messages.
As is, with no changes (curlifying quotes, fiddling
with text properties, prettifying,...). *Messages*
is a _log_.
2. We can add various ways for users or libraries to
optionally _view_ various subsets of such messages,
or to _filter_ (remove) them, or to _inhibit adding_
some of them.
But all of that needs to be optional, under control
by individual users or libraries, and _on top of_
an underlying/default behavior of recording every
echo-area message in *Messages* as is.
#2 has been discussed before, with no conclusions or
action taken.
I can't easily find the mail conversations about this,
and probably that doesn't matter - I think not much
that was concrete was proposed/discussed.
I did find these threads that touched on it, at least:
emacs-devel@gnu.org:
* Intelligent stacking of messages in the echo area
* Message's text-properties in *Messages*
* Why "symbol's value" error about a list?
Bug list:
* bug#40774: Error messages shouldn't be hidden when the user is idle
___
E.g., in the bug #40774 thread, I wrote:
I wonder if buffer *Messages* shouldn't have a menu-bar
menu, with a few items that do things like filter
temporarily in various ways, change `message-log-max',
etc. Some things a user might want to do with the buffer
content aren't necessarily obvious.
IOW, *Messages* could probably be made more directly
useful than it is now.
next prev parent reply other threads:[~2022-06-22 15:34 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
2022-06-22 15:34 ` Drew Adams [this message]
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=SJ0PR10MB5488567ECA5B8312259E5A79F3B29@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=55041@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=hmelman@gmail.com \
--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 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.