mirror of
https://github.com/Ark0N/Codeman.git
synced 2026-11-20 04:59:34 +01:00
Merge #834: codeman tui attaches by session name
codeman tui <name> attaches by an exact session name as well as by list number.
This commit is contained in:
commit
1207c316c0
11 files changed
+201
-17
No files matched your search
+10
@@ -18,6 +18,7 @@ tmux rather than proxying bytes.
|
||||
codeman tui # the dashboard
|
||||
codeman tui --list # print the numbered session list and exit
|
||||
codeman tui 2 # attach straight to session 2 of that list
|
||||
codeman tui api-docs # attach straight to the live session named api-docs
|
||||
```
|
||||
|
||||
The two fast paths are the scriptable ones.
|
||||
@@ -84,6 +85,15 @@ The same world through `--list`:
|
||||
The numbers are the same on both surfaces, so `codeman tui --list` then
|
||||
`codeman tui 4` is one thought.
|
||||
|
||||
A number moves as sessions change state; a name does not. `codeman tui <name>`
|
||||
attaches to the live session whose name is exactly `<name>` (case-sensitive,
|
||||
never a prefix, never the folder), so the same line gets you back into the same
|
||||
session from any folder or a fresh SSH login. Digits only always mean a list
|
||||
number. Session names are not unique in Codeman, so when two live sessions share
|
||||
the name it refuses and prints their numbers instead of guessing; a name only a
|
||||
RECENT row carries says the session has finished. Both refusals are printed
|
||||
before the terminal check, so a script can tell them apart without a TTY.
|
||||
|
||||
## The four groups
|
||||
|
||||
Groups are always in this order, and a session is in exactly one of them:
|
||||
|
||||
@@ -255,6 +255,7 @@ works well in SSH clients like Termius or Blink:
|
||||
```bash
|
||||
codeman tui # the dashboard
|
||||
codeman tui 2 # attach straight to session 2
|
||||
codeman tui api-docs # attach to the live session named api-docs
|
||||
codeman tui --list # numbered list, then exit
|
||||
```
|
||||
|
||||
|
||||
Reference in new issue
Block a user