Describe the bug
After enabling moving the autosave files to a separate directory:
(setq backup-directory-alist `(("." . "~/.emacs-backups")))
When editing a file that is autosaved the workspace/willRenameFiles is being triggered
with the original file as the oldUri and the backup location as the newUri.
With recent changes to lsp renaming this also messes up the imports for all files where the modified file is used and removes the package 😱.
A clear and concise description of what the bug is.
To Reproduce
Enable backup, (setq backup-directory-alist(("." . "~/.emacs-backups")))`
Enable lsp bsp trace. (create the
Create a file in with package in the package directory.
Modify the file. Save. Verify that the willRenameFiles message is sent.
Expected behavior
No willRenameFiles should be sent for backup.
Describe the bug After enabling moving the autosave files to a separate directory: (setq backup-directory-alist `(("." . "~/.emacs-backups")))
When editing a file that is autosaved the
workspace/willRenameFilesis being triggered with the original file as theoldUriand the backup location as thenewUri. With recent changes to lsp renaming this also messes up the imports for all files where the modified file is used and removes the package 😱.A clear and concise description of what the bug is.
To Reproduce Enable backup,
(setq backup-directory-alist(("." . "~/.emacs-backups")))` Enable lsp bsp trace. (create the Create a file in with package in the package directory. Modify the file. Save. Verify that the willRenameFiles message is sent.Expected behavior No
willRenameFilesshould be sent for backup.Screenshots
Logs
Related to https://github.com/scalameta/metals/issues/4888 lsp-metals version: 20221102.1628 lsp-mode version: 20230122.1747