When pasting a directory into a directory that already contains a directory with the same name Thunar currently merges both directories without asking, it should instead ask whether to merge or to rename the pasted folder.
Designs
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
As Guido said, at least on FreeBSD, clicking "replace" merges folders.
I don't mind additional click to get the functionality I'm used to, although I would prefer the possibility to configure it "old way" or "new way", something like "do not warn when merging folders" in preferences.
What I do mind is the confusion created by using word "replace". I am not native English speaker (although I take pride in my C2 certification), but "to replace" sounds like "put new in place of old". It's not exact "overwrite", but sounds more like "overwrite" than "put new to place of old, leaving old as well if there are no conflicts".
I think prompt should offer "merge", "overwrite" and "and "cancel", and should be opt-in in preferences.
However for some reason my concrete observations seem to differ from yours:
My setup:
test/folder/file1 (some text inside)
test/sub/folder/file1 (empty)
test/sub/folder/file2
Using STRG+C /STRG+V to copy "test/sub/folder" into "test" gives me, like before, the possibility to merge. I am asked to overwrite on each file.
Using DND or STRG+X /STRG+V to move "test/sub/folder" into "test" gives me, only the option to replace. No possibility to decide if single files are overwritten any more.
file1 will be replaced by an empty one. That is what I would expect from the "replace" button I pressed.
Do you see the same concrete behaviour on BSD, or something different ?
That change in behavior actually is a direct result of the fix of Bug #15727 before a copy was performed when a folder already existed, leading to time consuming operations. Now the old folder is deleted an a move is performed instead. A merge is not foreseen in that scenario.
Like before, it still would be nice to be asked to rename the existing folder, like this bug suggests.
Do you see the same concrete behaviour on BSD, or something different ?
I haven't done any thorough tests, just my use case, which never involves files of the same name, just folders of the same name with files of different names.
IIRC warning about replacing files existed before this change. But if there was no _file_conflicts, folders were silently merged.
After the change, warning about replacing folder happens, and - if there are no file conflicts - it gets merged after clicking "replace".
Hope this helps. I'd be glad to do further testing if needed.
IIRC warning about replacing files existed before this change. But if
there was no _file_conflicts, folders were silently merged.
Yes, exactly. That is still the case if you use CTRL+C and CTRL+V (copy) but not any more for CTRL+X and CTRL+V (move). Move will now ask you if it is fine to replace the folder.
After the change, warning about replacing folder happens,
Only for move, not for copy.
and - if there are no file conflicts - it gets merged after clicking "replace".
Negative, for me on "move", the folder is replaced, like the dialog says. Could you please re-test that use-case ?
In the latest thunar git, I can no longer merge folders by moving or copying. If I select "Replace" or "Replace All", it throws an error "Can't copy directory over directory".
This is particularly annoying when I'm trying to consolidate multiple folders with folders of the same name in another location (with the new thunar git, I have to go folder by folder recursively and manually move only the files).
Posting in this issue since they appear to be closely related. I can create a new bug report if needed.
I have no idea … this would require to dig into the code and/or the commit history.
Why replace? What about the Join-Dialog?
Basically the same answer. I doubt that they differ on purpose.
I suppose the right thing to do would be, to ask the user what to do: [Merge] [Replace] [Rename]
We already have an issue for that: #154
So let's close this one as a duplicate ... feel free to add additional info to #154 (ideally a patch or merge request )
Though, I am not sure if it is a good idea to introduce such a "directly rename" feature .. it's not very intuitive to directly popup a rename dialog. Probably it would indeed be better to first ask what to do. So we could reuse a dialog, like described in #154.
@lastonestanding
My other post was closed so I could not answer your question so I will answer it here if that is okay.
I was not aware that the "Replace" button doubles as a "Merge" button.
I would agree that to me this seems like it could be dangerous because both the Merge & the Replace actions are part of the same action, as opposed to how to how this is typically seen in other file managers.
Usually you get asked the question to merge and then after that if the two folders you are merging happen to contain items with the same names within them, you get asked again how you want to handle those identical named instances. In Thunar it just merges and replaces in one action, no questions asked, so not sure if taking the risk of using this button in this case. This is a rather old post so maybe not as important as I am viewing it.
Anyways just wanted to let you know that it was not a specific issue experienced as you asked, but just figured I would share my concern while I was here.