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 <juri@linkov.net>
Subject: bug#55041: 28.1; repeat-mode always prints message when enabled
Date: Wed, 22 Jun 2022 12:18:05 -0400 [thread overview]
Message-ID: <3AFCE543-FF0E-489A-A479-7BE3D25AB483@gmail.com> (raw)
In-Reply-To: <83y1xoit7d.fsf@gnu.org>
On Jun 22, 2022, at 12:00 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Howard Melman <hmelman@gmail.com>
>> Date: Wed, 22 Jun 2022 10:30:42 -0400
>> Cc: juri@linkov.net,
>> 55041@debbugs.gnu.org,
>> larsi@gnus.org,
>> stefan@marxist.se
>>
>> 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.
>
> I was talking only about desktop and ispell (the "those two" in your
> message to which I replied).
Apologies, I was talking about recentf and repeat-mode which Juri was asking
if I could inhibit messages for, so confusion all around it seems :)
>> 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.
>
> That's wrong attribution: I didn't reply to Stefan's message, I
> replied to yours.
I did not mean to imply that you were replying to StefanK, I was trying
to list all the offered opinions about removing the message (for
repeat-mode and possibly recentf) and I interpreted your reply as
being against doing so.
Howard
next prev parent reply other threads:[~2022-06-22 16:18 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
2022-06-22 16:00 ` Eli Zaretskii
2022-06-22 16:18 ` Howard Melman [this message]
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=3AFCE543-FF0E-489A-A479-7BE3D25AB483@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).