all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Basil Contovounesios via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "João Távora" <joaotavora@gmail.com>
Cc: 62694@debbugs.gnu.org, Michael Albinus <michael.albinus@gmx.de>
Subject: bug#62694: 30.0.50; eglot-tests fails with recent pylsp
Date: Sun, 09 Apr 2023 12:24:44 +0100	[thread overview]
Message-ID: <87bkjxguwz.fsf@tcd.ie> (raw)
In-Reply-To: <CALDnm53JgWRDAA6KZ1r-QyKrCqeCL8w4uDAeTELqse7oQPndUg@mail.gmail.com> ("João Távora"'s message of "Thu, 6 Apr 2023 20:50:56 +0100")

João Távora [2023-04-06 20:50 +0100] wrote:

> On Thu, Apr 6, 2023 at 6:39 PM Michael Albinus <michael.albinus@gmx.de> wrote:
>>
>> João Távora <joaotavora@gmail.com> writes:
>>
>> > Even if that's a problem for some hypothetical hardcore Debian
>> > user who happens to also be an Emacs developer and who uses pylsp
>> > but not in Eglot, and for some reason won't install anything from anywhere
>> > else in his development machine, we have yet to hear from the hordes of
>> > users at the intersection of all those conditions.
>>
>> The don't need to be pylsp users. A package could be installed for
>> several reasons.
>
> That could happen, but I doubt that pylsp is installed for any other
> reason than to be used.  To intersect the set of people who have
> installed it "accidentally" and additionally happen to be
> "make check"-running Emacs devs who are completely baffled when
> they see the failure.  Until I'm shown otherwise, I really think
> you're the only person in that set in the world, and you're not baffled:
> you know exactly what's going on.

Even if the user is far from baffled, each test failure that arises from
the test's logic or assumptions (rather than indicating a real problem)
is a drain on the user's time, so we should strive to avoid it.

-- 
Basil





  parent reply	other threads:[~2023-04-09 11:24 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06  9:55 bug#62694: 30.0.50; eglot-tests fails with recent pylsp Michael Albinus
2023-04-06 10:54 ` João Távora
2023-04-06 11:22   ` Michael Albinus
2023-04-06 12:49     ` João Távora
2023-04-06 14:58       ` Michael Albinus
2023-04-06 16:59         ` João Távora
2023-04-06 17:39           ` Michael Albinus
2023-04-06 19:50             ` João Távora
2023-04-07  7:44               ` Michael Albinus
2023-04-07 10:20                 ` João Távora
2023-04-07 10:29                   ` Michael Albinus
2023-04-07 10:47                     ` João Távora
2023-04-07 10:50                       ` Michael Albinus
2023-04-07 10:57                         ` João Távora
2023-04-07 11:04                           ` Gregory Heytings
2023-04-07 11:10                             ` João Távora
2023-04-07 11:11                           ` Eli Zaretskii
2023-04-07 11:20                             ` João Távora
2023-04-07 12:20                               ` Michael Albinus
2023-04-07 10:43                   ` Eli Zaretskii
2023-04-07 10:51                     ` João Távora
2023-04-07 10:53                       ` Michael Albinus
2023-04-07 10:59                       ` Eli Zaretskii
2023-04-07 11:06                         ` João Távora
2023-04-07 11:17                           ` Eli Zaretskii
2023-04-07 11:23                             ` João Távora
2023-04-07 11:37                               ` João Távora
2023-04-07 11:41                                 ` Michael Albinus
2023-04-07 11:47                                   ` João Távora
2023-04-07 11:53                                     ` João Távora
2023-04-07 12:07                                 ` Eli Zaretskii
2023-04-07 12:13                                   ` Michael Albinus
2023-04-07 12:22                                     ` Eli Zaretskii
2023-04-07 12:40                                       ` João Távora
2023-04-07 12:58                                         ` Gregory Heytings
2023-04-07 13:02                                           ` João Távora
2023-04-07 13:57                                         ` Eli Zaretskii
2023-04-07 12:59                                       ` Michael Albinus
2023-04-07 13:48                                         ` Eli Zaretskii
2023-04-07 13:57                                           ` Michael Albinus
2023-04-07 14:00                                             ` Eli Zaretskii
2023-04-07 14:04                                               ` João Távora
2023-04-07 14:33                                                 ` Eli Zaretskii
2023-04-07 15:06                                                   ` Michael Albinus
2023-04-07 19:05                                                     ` João Távora
2023-04-09 13:49                                                   ` Michael Albinus
2023-04-07 12:04                             ` Michael Albinus
2023-04-07 12:24                               ` João Távora
2023-04-07 12:47                                 ` Michael Albinus
2023-04-07 13:01                                   ` João Távora
2023-04-07 13:04                                     ` Michael Albinus
2023-04-09 11:24               ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2023-04-09 11:22       ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 12:41         ` João Távora
2023-04-09 13:21           ` Basil Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-04-09 14:45             ` João Távora
2023-04-09 15:32               ` Michael Albinus
2023-04-09 15:48                 ` João Távora
2023-04-09 16:08                   ` Michael Albinus
2023-04-09 18:17                     ` João Távora
2023-04-09 19:04                       ` Eli Zaretskii

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=87bkjxguwz.fsf@tcd.ie \
    --to=bug-gnu-emacs@gnu.org \
    --cc=62694@debbugs.gnu.org \
    --cc=contovob@tcd.ie \
    --cc=joaotavora@gmail.com \
    --cc=michael.albinus@gmx.de \
    /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.