0

Rename: allow to move file to not yet existing directories

Markus2021 2 weeks ago updated by Marc Strapetz 2 weeks ago 7

Make it possible to move a file already under version control to a newly created subfolder within the working copy which has not yet been added to version control because you do not allow empty folders to get added to version control.

I guess you are referring to Rename? I have updated the title correspondingly.

No, I'm not referring to rename. I'm referring to a file being somewhere in the working directory and already under version control and this file shall be moved into a newly created subfolder, which is not under version control yet. The name of the file stays the same and hence it is not a rename!

Which exact functionality would you use here, supposing that the directory already exists?

I would take an already existing file which is in a different directory and move it to that directory. The file is no longer where it was but in that directory afterwards. This is what users usually refer to if they talk about "move".

You can already move files using Rename, so we most likely won't add another redundant Move operation. Also, you have mentioned "move a file already under version control to a newly created sub-directory", hence I was assuming that you have already discovered the move functionality in the Rename ... what I can confirm is that Rename does not yet support to move to an untracked sub-directory. Hence, for me the most reasonable and smallest change to address this RFE is to change the existing Rename functionality to support that. Do you agree?

No I haven't discovered that yet. Rename is rename and move is move in my eyes. So I propose this one:

  1. Implement your suggestion
  2. Rename the menu item to Rename/Move to make it clear for beginners that it covers both

> Rename the menu item to Rename/Move to make it clear for beginners that it covers both


That sounds helpful. We will change this to "Move or Rename" for 22.1.