Both binaries take the same flags. They differ when run without one:
| Binary | Without flags |
|---|---|
tern-core |
Runs every pipeline |
tern |
Runs every pipeline when profiles exist; opens the TUI to create the first one otherwise |
Either binary works from any subdirectory: tern walks up to the
nearest directory holding .tern/ and runs from there.
| Flag | Short | Default | Effect |
|---|---|---|---|
--update |
-u |
Fetch and install every template in .tern/config.toml,
then exit |
|
--apply-templates |
-a |
Install every template from the cache without fetching, then exit | |
--force |
-f |
off | Convert every file, ignoring recorded modification times |
--follow-symlinks |
-s |
off | Follow symbolic links while scanning source trees |
--ignore-hidden-files |
-i |
true |
Skip hidden files and directories; -i false includes
them |
--profile-manager |
-p |
off | Open the TUI |
The usual cycle: tern -u after changing
.tern/config.toml or to pick up template updates, then
tern to convert, and tern -f after a template
change that should apply to files that did not change.