Acknowledged
4 months ago

VS Code: cannot rename project subfolder

- Windows 11

- SDK 8.1.0

- Monkey C extension 1.1.1

Use case:

- I want to make a copy of an existing folder (e.g. "resources/" => "resources copy/") and rename it (e.g. to "resources-spa/")

Recreation procedure:

- Open existing project in VS Code

- Copy/paste resources/ in place (CTRL-C, CTRL-V). This will create a copy called "resources copy"

- Rename "resources copy" to "resources-spa". The rename action will spin forever in VS Code - it may or may not complete if you close the VS Code window. (After you close the VS Code window, you can rename the folder by other means, such as using File Explorer or Terminal)

I suspect the Monkey C extension's language server is locking all of the project folders.

FlowState
Parents
  • 4 months ago

    > tested on Mac, there it works

    Thanks, I just tried this and found the same thing.

    Not surprising, as file-locking semantics are different in Windows vs Mac/Linux: in Windows if you lock a file, you will be prevented from renaming/moving any of its ancestor folders, but Mac/Linux will happy let you rename the parent folder of a locked file.

Comment
  • 4 months ago

    > tested on Mac, there it works

    Thanks, I just tried this and found the same thing.

    Not surprising, as file-locking semantics are different in Windows vs Mac/Linux: in Windows if you lock a file, you will be prevented from renaming/moving any of its ancestor folders, but Mac/Linux will happy let you rename the parent folder of a locked file.

Children
No Data