Take remote-chromium.sh's host as an argument instead of an env var
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
parent
b7ad3a9b8c
commit
9593b233aa
2 changed files with 13 additions and 5 deletions
|
|
@ -142,7 +142,8 @@ someone types the disk passphrase locally) unless something like
|
|||
|
||||
## Single remote app: Chromium with your logged-in accounts
|
||||
|
||||
`remote-chromium.sh` (run on the travel laptop) closes any Chromium you have
|
||||
`remote-chromium.sh [--x11] [host]` (run on the travel laptop; host defaults to
|
||||
`teemu-thinkpad-ubuntu`) closes any Chromium you have
|
||||
running on the home machine, then launches it there with its window drawn
|
||||
locally via `waypipe` (`--x11` for classic X11 forwarding instead). The close
|
||||
step matters: Chromium allows one process per profile, so a still-running
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue