Repository navigation
SnoutCode 1.0.7
Help when Git cannot sign in. When a pull, fetch, push or clone fails because Git could not sign in, SnoutCode now says why and how to fix it: a credential helper that cannot run (as in a repository copied from another computer), a token that was refused or is missing, a repository the account cannot see, or an SSH key or host key. Fix with hands Git's error to the console's agent, which checks your setup and walks you through signing in again. Open Terminal opens one in the repository.
The history of a file. Show History, on the file menus and in Git > Show History of File, narrows the Journal to the commits that changed a file, following renames. Click a commit to see that file's diff in it.
Open from the system. Files and folders open in SnoutCode from Open With, the Dock and Services on macOS, and from Explorer on Windows. A folder opens as the project; a file opens in a tab.
Searches see the whole build. Go to File and Find in Files now include the source folders a build compiles from outside the project folder, such as ../core/src/main/java. Go to File also takes wildcards: token*.ja finds TokenController.java.
Which file do I need?
| System | File |
|---|---|
| macOS on Apple silicon | SnoutCode-1.0.7-arm64.dmg |
| Windows, x64 | SnoutCode-1.0.7-windows-x64-setup.exe |
| Windows on Arm | SnoutCode-1.0.7-windows-arm64-setup.exe |
| Debian and Ubuntu | snout-code_1.0.7_amd64.deb or snout-code_1.0.7_arm64.deb |
| Arch Linux | snout-code-1.0.7-1-x86_64.pkg.tar.zst or -aarch64 |
SnoutCode updates itself to this version on macOS, and on Windows from 1.0.2. If you have 1.0.0 or 1.0.1 on Windows, install this one by hand: close SnoutCode first. The Windows installers are now code signed.