GNU bug report logs - #73355
29.4; eglot-rename reports success when it shouldn't

Previous Next

Package: emacs;

Reported by: Joost Kremers <joostkremers <at> fastmail.fm>

Date: Thu, 19 Sep 2024 12:02:02 UTC

Severity: normal

Merged with 73358

Found in version 29.4

Full log


View this message in rfc822 format

From: Joost Kremers <joostkremers <at> fastmail.fm>
To: João Távora <joaotavora <at> gmail.com>
Cc: 73355 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#73355: 29.4; eglot-rename reports success when it shouldn't
Date: Sun, 22 Sep 2024 00:04:52 +0200
On Sat, Sep 21 2024, João Távora wrote:
> On Sat, Sep 21, 2024, 13:13 Joost Kremers <joostkremers <at> fastmail.fm>
> wrote:.
>
>>
>> > It's possible Eglot is just successfully applying 0 edits.
>>
>> I guess that's one way of looking at it. :-)
>>
>
> I'm say this because Eglot has no logic to check if a rename is valid or
> not. It just does what the server tells it to. If the intended rename is
> invalid, the server can error out (and Eglot will tell you this) out return
> 0 edits. Either way, the server calls all the shots.

Ah, OK, I didn't realise that. So does the server report it made 0 edits?
If it does, would it make sense to have Eglot say no changes were made?

As soon as I have some time, I'll see if I can find out a bit more and
possibly take it up with the basedpyright people.

Thanks,

Joost


-- 
Joost Kremers
Life has its moments




This bug report was last modified 226 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.