Welcome to Vifm Q&A, where you can ask questions about Vifm usage. Registration is optional, anonymous posts are moderated. GitHub or Google logins are enabled.
0 votes
in vifm by

Hi again
long time no ask :)

recently discovered that when I use copy! or move! on a directory it replaces the whole content of the target (same named) directory , deleting any files and subfolders below
regardless if the source has same path or not

Would not that have more sense to only overwrite matching sub-elements
and not removing the others?
Or provide an option to that mode at least?

other file managers like mc prompt for the ovewriting the existing files, but never touch non-matching files.

Is there any solid reason why it is implemented differently in vifm?

1 Answer

0 votes
selected by
Best answer


sorry, I saw your question, but then forgot about it.

It's that way for historical reasons probably, before merging of directories was even there. Semantics of :copy and :move are basically to check for conflicts and know what to do about them beforehand. Putting files via p or P on the other hand is more interactive and has an option for merging directories.


p and P are good to use, once I know the merge option is there

Thank you


I wish :copy and :move would use the file conflict dialog.


I wish :copy and :move would use the file conflict dialog.

See https://github.com/vifm/vifm/issues/573 for a workaround.

If you would like to make a bug report or feature request consider using GitHub, SourceForge or e-mail. Posting such things here is acceptable, but this is not a perfect place for them.

Support Ukraine