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

Dear experts,

vifm Is my preferred file manager. I am now on Linux Lite 7.4 and am using a version that I recently compiled from source (Version: 0.14.3, compiled Aug 19 2025 -> latest commit available at that date).

When I yank an item and then paste/copy it to another location by pressing the "p" key I get an ascii warning popup stating:
"Background Process Error"
"cp: warning: behavior of -n is non-portable and may change in the future; use --update=none instead".

Since it is just a warning one can press Enter and the end result is as desired. However, since pasting files is an action that I perform with a certain regularity this message is becoming a small annoyance and I am looking for a way to suppress it.

The best (or actually, the only) option that I can come up with myself is to remap to the shell command i.s.o. using the built-in paste:
nnoremap p :!cp -rp --update=none %"r" %"d<cr>
At first glance this seems to work, though I have not tested it extensively yet. The clone command associated to the "C" key results in the same warning, but I haven't figured out yet how to remap that one due to the [count] part that may precede it.

What is the advice of the experts w.r.t. suppressing the persistent warning popup? Is the remap mentioned above ok, or is there a better way to suppress the "may change in the future" warning?

Thanks so much for this awesome software and all the hard and terribly appreciated work in maintaining it as well as the Q&A forums!

ps.
My apologies if this is a repeated question.

1 Answer

+1 vote
by

Hello,

Thanks for your kind words and bringing this to my attention, I wasn't aware coreutils had this change of behaviour and a new warning. Will have to take it into account.

Adding set syscalls (docs) to your configuration should address the issue by not using cp for copying.

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