Welcome to Vifm Q&A, where you can ask questions about using Vifm. Registration is optional, anonymous posts are moderated. E-mail and GitHub logins are enabled.
0 votes
in vifm by
edited by

Hello,
I am using these commands for copy and move with and without conflict menu:

" Copy files with conflict menu
command! mCopyWithConflictMenu :yank | winrun , put

" Move files with conflict menu
command! mMoveWithConflictMenu :yank | winrun , put!

" Copy files in background
command! mCopy :copy&

" Move files in background
command! mMove :move&

They work fine. I have some questions:

  1. Are there any differences in terms of speed and memory usage between them? (between :copy and :yank | winrun , put)

  2. mCopyWithConflictMenu copies in foreground and it blocks the GUI. I added & at the end which resulted in similar behavior as :copy (background copy with no conflict menu).

  3. Is there a way to execute a background copy and make it to show the conflict menu, only if there is a conflict? This way one hotkey can be used.

  4. When executing mCopyWithConflictMenu, on the status bar it says press i for details, but when I press i, it doesn't do anything.

Thank you

1 Answer

0 votes
by

Hi,

Are there any differences in terms of speed and memory usage between them? (between :copy and :yank | winrun , put)

Part of the code is different, so there must be differences, but they should be negligible.

mCopyWithConflictMenu copies in foreground and it blocks the GUI. I added & at the end which resulted in similar behavior as :copy (background copy with no conflict menu).

That's not a question :)

Is there a way to execute a background copy and make it to show the conflict menu, only if there is a conflict? This way one hotkey can be used.

No, since their introduction and at least until today background operations are non-interactive. They check for conflicts beforehand and then just execute operations with minimal checks.

When executing mCopyWithConflictMenu, on the status bar it says press i for details, but when I press i, it doesn't do anything.

Both :yank | winrun , put and :mCopyWithConflictMenu seem to work for me. What version of Vifm are you using?

by

I am using

Version: 0.14
Git info: v0.14-37-g8e5de61d9605-dirty
Compiled at: Mar 29 2025 00:12:23

With executing :mCopyWithConflictMenu, it shows the progress status on the statusbar. Once I press i, it progress freezes (no more changes in the numbers).

In vifm, whenever I press i, it enters the folder or runs the file.

Any suggestions? Thanks

by

That revision works identical for me. What if you do yy and p manually, does i work in this case? Also, what are you copying, a single file or a directory structure (both behave the same for me though)?

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.
...