unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "João Távora" <joaotavora@gmail.com>
To: Federico Beffa <federico.beffa@fbengineering.ch>
Cc: 73500@debbugs.gnu.org
Subject: bug#73500: eglot: diagnostic location not always shown
Date: Mon, 30 Sep 2024 16:32:36 +0100	[thread overview]
Message-ID: <CALDnm52c5kKx6fb4gmV459g8Q_a+zWcq3WTXu+LRd9sDh2dqxQ@mail.gmail.com> (raw)
In-Reply-To: <94ba9918-e18f-4e29-ad6e-b46286a55630@fbengineering.ch>

On Mon, Sep 30, 2024 at 1:08 PM Federico Beffa
<federico.beffa@fbengineering.ch> wrote:
>
> On 30/09/2024 13:21, João Távora wrote:
>
> On Mon, Sep 30,
>>
>>
>> From all your previous replies I expected these answers. Dismissing bug reports without making any serious effort to reproduce them just makes a disservice to your own and to the Emacs projects.
> I didn't dismiss you bug report, I simply couldn't reproduce. I'm sorry my performance and engagement has not lived up to be your standards. You're welcome to speak to my manager and recommend a pay cut from 0 to 0.
> Well, let's be honest.

Yes, let's :-)

> You didn't try seriously: did you install all required software? No.

Should I have installed a Nix Linux distro or ghcup distribution to
get exactly those versions?  I used my Archlinux package manager.
Seemed "serious" enough to me.  I installed a working version of
haskell-language-server which proved to be working correctly and
interfacing with Eglot correctly, sending diagnostics similar to the
ones you reported.

> You did see the logs and screenshots proving the problem?
> Yes, but arbitrarily decided that I was making things up,
> which is false.

I didn't say you made it up.  Why would you? I said the screenshot
you provided was not of Emacs -Q, which is plain to see.

Your Emacs -Q recipe is emacs -Q -l init.el` where init.el is

  (use-package haskell-mode :ensure t)

Did you run this yourself?  I don't think it will produce an Emacs
that has yasnippet, company, whatever WK is, a non-default font size
and possibly a lot more customizations. It won't turn on wombat-theme
as you mentioned (and note that a theme is also a potential culprit,
as it can run arbitrary lisp code).

And what do screenshots help anyway?? I didn't even request
screenshots.  I can't debug a screenshot.  Noone is doubting
your affliction is real, it's just that no one is obliged to stop what
they're doing IRL to help you either.

> You're probably angry due to the code lens thread.

Why on earth would I be angry about that?

> And, by the way, I also have and sometimes still do contribute to open
> source projects without any remuneration.

Good for you.

> That doesn't justify such a toxic behavior and answers.

Get yourself a mirror.  Accusing someone who has spent _any_ amount
of unpaid time analysing your report of not having  making a serious effort
is not a nice thing to do.

> Most of the time developers are thankful for bug reports, not dismissing them out of pride or whatever.

And I am thankful, which is why I thanked you for the recipe, didn't I?
I didn't ask for the bug to be closed, did I?  You'll just have to do the
investigation yourself or wait for someone with enough time or the Nix
system to do a better analysis.  Be patient, sometimes that helps.
(and not harassing maintainers also helps).

You can also follow my recommendation of using Emacs -Q.  I also
suggested you try out my version of Main.hs to see if you get the
underline  I see. You're free to ignore these suggestions but they are
the best I can do with the time I have available.

If that doesn't live up to your standards I'm very sorry, but ultimately
I don't care about what standard of technical support you think
you are entitled to as an Eglot user.

João





  reply	other threads:[~2024-09-30 15:32 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-26 13:49 bug#73500: eglot: diagnostic location not always shown Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-28 11:16 ` Eli Zaretskii
2024-09-28 11:47   ` João Távora
2024-09-28 15:23     ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-28 21:18       ` João Távora
     [not found]         ` <452a24b1-14e8-40a6-b921-a26522278a82@fbengineering.ch>
2024-09-29 17:20           ` João Távora
2024-09-29 18:59             ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-29 21:18               ` João Távora
2024-09-30  9:19                 ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-30  9:41                   ` João Távora
     [not found]                     ` <bee5efd8-c015-43d1-b37d-392d4ffc08d7@fbengineering.ch>
     [not found]                       ` <CALDnm501CMXD8x_9s6Hm0fD5_+K4wmH58t7wXf5buKDuU+=vGg@mail.gmail.com>
2024-09-30 12:08                         ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-30 15:32                           ` João Távora [this message]
2024-09-30 15:45                       ` Federico Beffa
2024-10-01 16:08 ` Dmitry Gutov
2024-10-01 16:32   ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-01 19:48     ` Dmitry Gutov
2024-10-01 20:18       ` Federico Beffa via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-01 20:39         ` Dmitry Gutov

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=CALDnm52c5kKx6fb4gmV459g8Q_a+zWcq3WTXu+LRd9sDh2dqxQ@mail.gmail.com \
    --to=joaotavora@gmail.com \
    --cc=73500@debbugs.gnu.org \
    --cc=federico.beffa@fbengineering.ch \
    /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).