Northern Commander

While an operation runs

A copy, move or delete runs while you carry on. A panel watches it while you want to; send it to the background, and the line under the panes goes on showing it.

The top bar is the whole copy, the one under it the file it is on.
KeyAction
⌘JAttend to the waiting operation
EscCancel operation
⇧⌘JJournal

The panel

Its title is what it is watching: Copy, Move or Delete.

First bar
The whole of it: bytes of bytes, and items of items. What is done is written in the unit of the whole, 0.81 of 2.25 GB, so the two read against each other. Work that moves no bytes — a move within one disk, a delete — counts items only.
Second bar
The file it is on, and how much of it is done.
The line under them
How fast it is going and how long the rest should take. In place of that: Waiting for you while a question is up, Paused, Waiting for the disk while it waits its turn, Waiting for film.zip’s earlier change to finish behind another change to that archive, Writing to the device or Removing the originals at the end of a copy or move, or why it failed.
A last line
For work that takes only the files that match, how many it has left out so far.

The panel closes itself when the work is done, or stopped. There is no summary: everything skipped was asked about as it happened, and all of it is in the journal. Only when the work failed as a whole — the disk would not confirm what was written, say — does the panel stay, saying why, until Close.

Pausing and stopping

  • Pause holds it where it is — between files, or part-way through a big one. Resume carries on.
  • Stop, or Esc on the panel, pauses it first, then asks whether to stop. Saying no lets it carry on — or stay paused, if it was.
  • While a question is up, the panel behind it cannot be reached. The question has its own Stop.
Stopping Leaves
A copy What has been copied stays. The file being copied now is removed, and the rest are not copied
A move, originals removed all at once The files copied so far stay at the destination as copies, and every original is still where it was
A move, originals removed as it goes What has been moved is at the destination and gone from where it was. The rest stay where they are
A delete What is gone is gone. Everything else is where it was

Which kind of move it is, is Move removes originals. What a stopped operation did not finish stays marked, so pressing the same key again carries on rather than starting over.

In the background

Background on the panel sends it out of sight; Background on the copy dialog starts it that way. Either way, the rows it came from are unmarked at once, and the line under the panes shows it.

A copy going on out of sight: the file it is on, how far it has got, and how fast.
  • The line says paused, queued or needs you after its name, and +2 queued when more is waiting behind it.
  • Esc in the panes brings a copy, move or delete back with the question its Stop asks — or, when it is waiting on a question, with that one. Working out a folder’s size, or a search, stops at once.
  • One that failed stays on the line, with why, until Esc clears it.

A question while you were away

A copy in the background that meets something it has to ask about — a file already there, one it cannot read — does not put a dialog in front of whatever you are typing into. It waits, and the line says so.

Stopped on a question, until you come back to it.

⌘J brings its panel back, with the question in front of it. With nothing waiting on an answer, the key does nothing.

Several at once

Each disk takes as much at once as suits it. On the Mac’s own drive several operations run side by side. On a disk you can eject — a memory card, a USB stick, an external drive — they take turns: the next one waits, says queued, and starts when the one before it is done. A network share takes one or two at a time. Work on different disks runs side by side.

Working out a folder’s size, when you mark it, goes through the same queue, and shows on the same line.

Quitting while something runs

Quitting asks first, listing what is still running, and starts on Stay. Quit anyway stops each operation and waits for it to finish or remove what it was writing — however long a slow card takes — and Quit now then leaves whatever has not stopped as it is.