contacts --sort takes place and hash; the Archived list gets the PLACE column

The CLI sorts on the same ring as the Contacts screen (name, heard, packets,
place, hash). The ring moved to ui/widgets.py so the CLI loads no TUI code, and
ordered_contacts sorts by place (no place last) and by key.

The Archived list reads NAME · ARCHIVED · PLACE · KEY, sorts by place, cuts no
value and pans with ←→, like the Contacts list. The place fill and its live
refresh moved from ContactsScreen into ContactListScreen, so any list that
declares the PLACE lane gets them from places=.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
Jean-Pierre MartineauandClaude Opus 5.5 committed 2026-11-03 17:28:01 -05:00
1 parent 2df3dd2c39
commit d08513aa69
10 files changed
+299 -113

No files matched your search

+3 -3
View File
@@ -563,7 +563,7 @@ $ meshterm contacts --sort bogus
Usage: meshterm contacts [OPTIONS]
Try 'meshterm contacts --help' for help.
Error: Invalid value: --sort must be one of: name, heard, packets (got 'bogus')
Error: Invalid value: --sort must be one of: name, heard, packets, place, hash (got 'bogus')
```
**A confirmation that you did not give** is in the same class, because nothing has
@@ -624,7 +624,7 @@ $ meshterm contacts --sort bogus --json
Usage: meshterm contacts [OPTIONS]
Try 'meshterm contacts --help' for help.
Error: Invalid value: --sort must be one of: name, heard, packets (got 'bogus')
Error: Invalid value: --sort must be one of: name, heard, packets, place, hash (got 'bogus')
$ echo $?
2
```
@@ -894,7 +894,7 @@ The contacts that your device knows.
| Option | What it does |
| --- | --- |
| `-s`, `--sort ORDER` | `heard` (default), `name`, or `packets`. |
| `-s`, `--sort ORDER` | `heard` (default), `name`, `packets`, `place`, or `hash` (the key). |
```console
$ meshterm contacts --sort name