From: "Basil L. Contovounesios" via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: 56641@debbugs.gnu.org
Subject: bug#56641: Deprecate `lsh`
Date: Sun, 24 Jul 2022 06:38:08 +0300 [thread overview]
Message-ID: <87y1wjuqn3.fsf@tcd.ie> (raw)
In-Reply-To: <47492CDF-AFFA-4B72-9C6F-61A2EE545791@acm.org> ("Mattias Engdegård"'s message of "Sat, 23 Jul 2022 18:51:14 +0200")
Mattias Engdegård [2022-07-23 18:51 +0200] wrote:
> 23 juli 2022 kl. 17.42 skrev Basil L. Contovounesios <contovob@tcd.ie>:
>
>> Thanks, but the warnings are being stubborn with and not listening to
>> me. Could you please have a word with them?
>
> A serious conversation was held and some very frank words were pronounced.
Is there an RFC for that protocol? It seems to be effective.
>> First, they are a bit repetitive in parallel 'make -j8 check':
>
> That was made on purpose to really hammer the point home.
Is it a bug that we don't consistently do that for all warnings?
>> For the `mapcar' case, only the `mapcar' function can be used in
>> the symbol list. For `suspicious', only `set-buffer' can be used.
>> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> Clearly you aren't suspicious enough.
But enough to not be suspiciously unsuspicious.
>> How can these issues be addressed?
>
> Why, `git pull` of course!
I picked some of that up from my local pharmacy, and...
> (Sorry about all this, and thanks a lot!)
...WFM, thanks! No need to apologise,
--
Basil
prev parent reply other threads:[~2022-07-24 3:38 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 13:38 bug#56641: Deprecate `lsh` Mattias Engdegård
2022-07-19 13:52 ` Eli Zaretskii
2022-07-19 14:44 ` Stefan Kangas
2022-07-19 15:40 ` Eli Zaretskii
2022-07-19 15:53 ` Mattias Engdegård
2022-07-19 16:20 ` Stefan Kangas
2022-07-19 16:38 ` Eli Zaretskii
2022-07-20 1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 2:36 ` Eli Zaretskii
2022-07-20 3:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 11:24 ` Eli Zaretskii
2022-07-20 11:57 ` Mattias Engdegård
2022-07-20 12:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 12:44 ` Eli Zaretskii
2022-07-20 14:30 ` Mattias Engdegård
2022-07-21 1:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-21 7:47 ` Mattias Engdegård
2022-07-23 7:26 ` Lars Ingebrigtsen
2022-07-23 10:32 ` Mattias Engdegård
2022-07-23 11:20 ` Lars Ingebrigtsen
2022-07-23 13:18 ` Eli Zaretskii
2022-07-23 13:20 ` Lars Ingebrigtsen
2022-07-23 15:42 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 16:51 ` Mattias Engdegård
2022-07-24 3:38 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
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=87y1wjuqn3.fsf@tcd.ie \
--to=bug-gnu-emacs@gnu.org \
--cc=56641@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=mattiase@acm.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 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).