Northern Commander

Copying and moving

How long a copy, a move, a rename or a delete waits for the device — the disk, card or drive — to have what it did before it says it is done, when a move to another volume removes the originals, and, for changing an archive, what becomes of its old copy and whether to ask first.

Copying and moving, in the settings. The line under the list explains the setting the cursor is on.

What is written goes first to macOS, which puts it on the device a moment later. Until then, pulling the device out or losing power can lose it — so by default each operation waits once, at the end, for the device to have everything. That wait is what makes done mean it is safe to eject.

  • Leave them as they are for most work. The wait at the end takes a fraction of a second.
  • Choose each file as it goes for a card or a drive that may be pulled out or lose power partway, where every finished file must be whole on it.
  • Choose none only for work you would simply do again. Ejecting still writes everything out.

They are on the settings screen — Options › Settings…, or Settings… in the application menu, ⌘, — under Copying and moving, and in settings.json.

Move removes originals moveOrder

When a move across volumes removes the originals: once all is copied, or file by file.

Default: all at once · all at once, as it goes

Only a move to another volume has originals to remove. Within one volume, a move just renames.

Value The originals go A move stopped partway has left
all at once Together, once every file is copied and the device has been waited for as Move waits for device says. Once they start going they are not stopped halfway, and the status line says removing the originals The copies, and every original where it was
as it goes Each as soon as its own copy is in place Some files moved, and the rest not yet

With as it goes, a copy is on the device before its original goes only when Move waits for device is each file as it goes. Either way, a file that fails to copy keeps its original.

From the next move you start.

Copy waits for device copyFlush

When a copy waits for what it wrote to reach the device. More waiting is slower and safer.

Default: volume at the end · none, volume at the end, each file at the end, each file as it goes

Value A copy waits for the device
none Never. It is done when macOS has what was written, and ejecting writes it out
volume at the end Once, when every file is written, for the whole volume. It takes a fraction of a second, and covers the files’ names as well as what is in them
each file at the end When every file is written, for each file in turn. It does not cover their names
each file as it goes For each file before it takes its name, so no file ever has its finished name with less than all of it on the device. The slowest: many small files take many times as long

While it waits, the status line says writing to the device. Every choice but none also waits every 64 MB of a big file as it is written, so stopping a copy is not followed by a long wait.

If the device will not confirm, the copy fails: its files are in place, but nothing can say they are on the device. From the next copy you start.

Move waits for device moveFlush

When a move across volumes waits for what it wrote to reach the device.

Default: volume at the end · none, volume at the end, each file as it goes

The copying half of a move to another volume, as Copy waits for device is for a copy. Within one volume a move only renames — that is Rename waits for device.

Value A move waits for the device
none Never. The originals can be removed before the device has the copies
volume at the end Once, when every file is copied, for the whole volume — before any original is removed, when Move removes originals is all at once
each file as it goes For each file before it takes its name, and before its original is removed

each file at the end is not offered for a move. Every choice but none also waits every 64 MB of a big file as it is written.

From the next move you start.

Rename waits for device moveWithinVolumeFlush

When a rename, or a move within one volume, waits for the new names to reach the device.

Default: volume at the end · none, volume at the end

A rename, and a move within one volume, change only names — so the only wait there can be is for the whole volume.

Value A rename or a move within one volume waits
none Never. Ejecting writes the new names out
volume at the end Once, when it is done, for the device to have the new names

From the next rename or move you start.

Delete waits for device deleteFlush

When a delete waits for what it removed to be gone from the device.

Default: volume at the end · none, volume at the end

A delete changes only names, whether to the Trash or for good — so the only wait there can be is for the whole volume.

Value A delete waits
none Never. Ejecting writes the change out
volume at the end Once, when it is done, for the device to have it. It takes a fraction of a second

If the device will not confirm, the delete is reported as failed, though what it removed has gone. From the next delete you start.

Old copy of an archive oldArchive

A change inside an archive writes it again. Whether its old copy goes to the Bin, so the change can be undone, or is deleted.

Default: bin · bin, delete

Ask before changing an archive askBeforeChangingArchive

Ask before anything is copied into, deleted from or renamed in an archive.

Default: off · on or off