About, updates and reports
What this copy is and where it keeps its files, getting the newest version, and telling us about a problem or what you think. All four are in the Options menu and in the application menu — the menu macOS puts under the application’s name.
About
About, in the Options menu, or About Northern Commander in the application menu.
- Version
- This copy’s version.
- Copyright
- Who owns it, under the version.
- Settings
- Where the settings file is.
~is your home folder. - Logs
- Where each run of the application writes its log — see Support for reading them.
- License, Privacy, Notices
- Open in the viewer the texts this copy carries: the terms it is used under, what it sends, and the licenses of what is inside it. They are the License, Privacy and Notices pages here.
Updates
Check for updates… — in the Options menu and the application menu — looks for a new version now, and says what it found either way.
- By itself, it looks once a day while Check for new versions is on — once you have said it may. The welcome asks the first time the application opens, and turning the setting on is saying yes. A check it makes by itself says nothing unless there is a new version.
- Which versions is Versions to be offered: stable, finished releases only, which is what you get unless you choose otherwise, or beta, those and the ones being tried out first. A finished release replaces a beta, so beta never leaves you behind. Version 1.0.0 moves every copy to stable once, so choose beta again after updating if you want betas.
- What a check sends is one request, for the list of releases — nothing about you or your Mac. See Privacy.
- A new version is shown in macOS’s own windows rather than on the text screen, with the choice of installing it now. After a check you asked for, that window opens in front of the application. Installing it closes the application and opens the new version.
- Every update is checked against the key this copy was built with, and one that does not match is not installed.
- A copy built from the source code has no updater, and Check for updates… says so.
- While checks are off, Check for new versions and the welcome’s box say in red that updates include bug fixes, and that without them you stay open to problems that are already fixed.
What’s new
The first time a newer version starts, Northern Commander was updated says what changed. It opens after you have agreed to the license and once per version.
- The notes, on the left: the version you came from and the one now running, anything to take note of first, then each highlight under its title. They scroll when long; PgUp, PgDn, Home and End scroll them from wherever the focus is.
- A product, on the right: another from Outonomy, or Outonomy itself if you have them all.
- A tip about Full Disk Access, below the notes, while it is off.
The buttons:
- Close closes it. Esc does too.
- Release notes opens the same stretch of versions on the website, every entry of it.
- Known issues and Recently resolved open those two lists on our public support repository.
An update that only fixes things shows no screen. A one-line notice says which version you are on and how many fixes it brings.
When this version is old
Once the version running is more than six months past the day it was built, Update overdue comes up at start. It says that newer versions fix problems found since, and that going without them leaves those problems yours to bear. It stands in for What’s new, which is not shown for a version that is already old.
- Check for updates runs the same check as the menu item. A copy built from the source code does not have it.
- Go to downloads opens the website’s download page.
- Not now closes it. Esc does too.
However it is closed, it stays away for two weeks, and comes back after that for as long as the version is old.
Reporting a problem
Report a problem… — in the Options menu and the application menu — sends us a private report of what went wrong. Everything that goes with it is on the screen first, and nothing goes until you press Send.
- Problem
- What went wrong, and what you were doing. The one thing a report must have. Enter starts a new line here; ⌘Enter sends.
- Email (optional)
- Only if you would like an answer. One that does not look like an address is pointed out as you type, and Send waits until it is put right or taken out.
- Also sent
- This copy’s version and kind, the version of macOS, and your Mac’s processor type.
- Crash-report identifier
- There when your crash reports carry one — while they are sent automatically, or once a kept one has been sent. Ticked, it lets us find the crashes your description is about. See Privacy settings.
- The log of the run that started…
- The logs of the last two runs, this one among them, each ticked. See contents opens one in the
viewer exactly as it would go: your home folder is written
~, and a very long one keeps its most recent part.
The buttons:
- Send sends it. While it goes, Esc waits rather than leave it half sent.
- Open support opens our public support repository in your browser, for asking in the open instead. What you wrote stays here.
- Known issues opens the list of what we already know about, to look through before you send. What you wrote stays here.
- Cancel closes it and sends nothing.
Once it has gone, Report sent gives it a reference, like NC-7Q2K-M4XD: quote it if you write to
us at support@northerncommander.com. Copy reference copies it, and Open in browser opens the
support repository. If the report arrived without its log, the screen says so.
If it could not be sent, Report not sent says why and offers another way. Save as file puts the report in your Downloads folder and shows it in Finder; Write email starts a message to support@northerncommander.com to attach it to. Back returns to what you wrote, still there to try again.
Support has what a report holds and what becomes of it; Privacy has how it is kept.
Sending feedback
Send feedback… — beside Report a problem… in both menus — is for what you think rather than what went wrong. It sends no logs.
- This is
- Something annoying, Something you like, or A suggestion, which it starts on.
- Saying
- What you think. The one thing it must have. Enter starts a new line; ⌘Enter sends.
- About
- The part it is about: Panes, Viewer, Editor, Terminal, Search, Settings or Elsewhere.
- How important
- A small thing, which it starts on, A real difference, or It is blocking me.
- Email (optional), Also sent
- As for a problem.
Open discussions opens the public discussions on GitHub instead. Once it has gone, Feedback sent gives it a reference, as a report does, and Feedback not sent offers the same file and email when it could not go.