In the Nautilus file manager (Files 3.6.3), when dragging and dropping a file into a directory, the behaviour appears to be dependent on the file-system location of the target folder. (either local or remote)
Dragging and dropping to a local directory triggers a "move" of the source item, and this is the behaviour that I am used to and prefer.
But if the target directory is a remote directory, for example on an NFS mount, then it triggers a "Copy" action. As it's not immediately obvious from the icon or context that the directory is remote, and further that the copy action might take some time, I am often left with the source files in place, and I don't notice that has happened until later. This is undesirable.
I am aware that I can force a "Move" action using a
Drag, and also that I can force a move using the
mv command line.
However I wish to configure Nautilus to attach the "Move" action to the drag and drop of a file to a remote directory. For me, this is the most common use case, and simplest and most efficient way to achieve that.
I understand that this choice to default to copy-for-remote-targets may have derived from a desire to ensure the consistency of the operation. However it breaks the abstraction of the common interface provided by the virtual file system.
I am looking for the configuration options that control that behaviour.