Iñaki Arenaza

I have hit this same issue, and I have dug a bit into it. Pull request #1762 introduced the changes that, if I am not mistaken, are at the root...

Interestingly enough, if you perform an equivalent[1] operation, but use `lsp-rename` to rename the Clojure namespace instead of renaming the file, the response from the LSP server includes the same...

> So maybe `clojure-lsp` should be returning that second map too[2], for this type of operation? (`willRenameFiles`) Humm it seems I was wrog. If I'm reading https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#workspace_willRenameFiles correctly, the returned...

These changes seem to make it work as expected: ```diff Unstaged changes (1) modified lsp-mode.el @@ -4310,20 +4310,8 @@ interface TextDocumentEdit { (f-delete (lsp--uri-to-path uri) recursive?))) ("rename" (-let* (((&RenameFile :old-uri...

I just had an instance of this, and I "instrumented" `abort1` to have a look at why the exception was thrown. Basically a created a `def` with the content of...