The two-pane browser
Every connected tab shows the two-pane browser: your Mac on the left, the server on the right. Both panes work the same way, whichever protocol the remote side speaks.
Navigating folders
Section titled “Navigating folders”- Double-click a folder to open it.
- ⌘↑ goes to the parent folder, ⌘↓ or ⌘O opens the selected entry.
- The path bar above each pane shows the current path; type a path into it and press ⏎ to go there. ⇥ completes the path from what exists, ⇧⇥ cycles back through the candidates, ⎋ cancels the edit.
- A local folder opens as fast as it can be read, with sizes and dates filling in as they are found rather than holding up the whole listing.
Columns and sorting
Section titled “Columns and sorting”Columns can be sorted by clicking their header. The Type column shows what each row is — file, folder, symlink, or bucket — and a bucket gets an icon of its own.
Hidden files
Section titled “Hidden files”⌘⇧. shows and hides hidden files in both panes.
Search
Section titled “Search”⌘F opens the search field for the pane; ⎋ clears it.
Transferring from the browser
Section titled “Transferring from the browser”- Drag files from one pane to the other, or from either pane into the Finder.
- Press ␣ (space) to transfer the selection to the other pane.
- The file actions sit under a three-dot menu; ⌘⌫ deletes the selection.
When a folder cannot be opened
Section titled “When a folder cannot be opened”The message above the pane is one sentence in the language macSCP is running in — for example that the folder listing the server sent could not be read, or that the connection starts at the bucket list and the path has to name a bucket. In v1.5.0 the same failures were shown as a category and a sentence after it, in English; the category is gone and the sentence says what happened.
Info and permissions
Section titled “Info and permissions”⌘I opens the info sheet for the selection, with sizes, dates, and — where the protocol supports it — a permissions editor. On S3, the editor follows what the store’s capability actually allows and says so where there is none.
Checksums
Section titled “Checksums”Add the optional checksum column to a pane and macSCP computes a checksum for a file, or a whole selection, on request. Every number is labelled with where it came from:
- computed here — macSCP read the file and hashed it itself,
- computed on the server — the SSH server ran the algorithm’s tool for it,
- read from the object store’s tag — the S3 object already carried one.
A host without the algorithm’s tool says so instead of failing silently. See Transfers for what else the browser feeds — the checksum ledger survives a reconnect per tab, not across sessions.