Concepts
Words
| Word | Meaning |
|---|---|
| Project | A named group of tabs with a root directory, usually one codebase. |
| Tab | One layout of panes inside a project. |
| Pane | One terminal running one program. |
| Placement | Where a pane is: tiled in the layout, floating above it, or minimized. A pane moves between the three without restarting. |
| Dock | The strip at the bottom of the window that holds minimized panes. |
| State | What a pane is doing: idle, running, waiting, done, failed, exited. |
| Attention | A pane that needs you: one that's waiting, done or failed. |
| Daemon | The background process that owns everything. The window calls it the server. |
| Hub | The one machine the others connect through. It runs isc hub, which serves the page and lets your devices and other machines in. |
| Machine | A computer running insensical: this one, one joined to your hub, or one reached over ssh. |
| Device | Something you look from that has no insensical of its own, such as a browser, paired with your machines by its key. |
The daemon
- The first window or
isccommand that needs it starts it. It runs in its own session and outlives whatever started it. isc daemonruns it in the foreground. A second daemon on the same socket refuses to start and says "a daemon is already running".- It owns the projects, tabs, panes and layout. Anything a window does, a command can do, and each sees the other's changes at once. It does no work while idle.
- On Linux with systemd, a daemon started by a window or command runs in a scope of its own (
insensical-daemon-…insystemctl --user), so closing the terminal that started it takes neither it nor your programs. A logout that stops your user manager does, unless lingering is on (loginctl enable-linger). On a different socket,INSENSICAL_SCOPE=1gives the same scope andINSENSICAL_SCOPE=0turns it off. - Stopping it kills your programs.
isc kill-serveror a termination signal ends every program in every pane and keeps the layout for the next start. Moving it to a new version stops nothing. Stopping, restarting and new versions covers both.
Who can reach it.
- Only your user can connect. It listens on its socket and on no network.
- Any program running as you can drive it through the socket: open and close panes, type into them and read them.
- For another machine, go through
ssh: see Other machines, over ssh. For a browser, startisc hub, a separate program that listens on this machine only: see In a browser.iscand the interface in a terminal can use another machine's daemon, and the window shows other machines' projects beside this computer's: see Other machines in the window.
The socket.
- Its directory must be owned by you and closed to others (
0700). The daemon creates it that way and refuses to start, saying why, if the directory is wider, is a link, or holds something that isn't a socket where the socket goes. - Paths are limited to about 108 bytes on Linux and 104 on macOS. A longer
INSENSICAL_SOCKETfails with "path must be shorter than SUN_LEN". - With neither
INSENSICAL_SOCKETnorXDG_RUNTIME_DIRset (TMPDIRon macOS),iscfails with "no per-user runtime directory".
The daemon's environment
The daemon has the environment of whatever started it, and every pane inherits it.
- Started from a launcher, panes get the launcher's
PATH, not a login shell's, so a command other terminals find might not be found. - On macOS, a new pane's shell starts as a login shell. A
shellsetting runs exactly as written and needs its own-l. - A variable you change in a shell profile reaches new panes through the shell's own start-up files, or after
isc kill-serverand a restart from an environment that has it. That kills every program. - Moving the daemon to a new version keeps its environment.
INSENSICAL_HOSTisn't passed on, soiscin a pane means that pane's own daemon. Ignored signals aren't passed on either.- Started by the user unit, the daemon has systemd's user manager environment, which reads no shell profile:
PATHis usually short, and variables from~/.profileare missing.systemctl --user show-environmentprints what it has. To add to it, runsystemctl --user import-environment PATHbefore the unit starts, or putEnvironment=lines in a drop-in fromsystemctl --user edit insensical.
The hub, machines and devices
These let you reach your machines from one place.
- One of your machines is your hub: where
isc hubruns, reachable by your devices on your network, your tailnet or the internet. - Your other machines join it:
isc hub inviteon the hub makes a line, andisc hub joinon the other machine takes it. A joined machine doesn't listen on the network; itsisc hubdials the hub. - A device pairs with the hub once, by a code, and is known by its key from then on. It reaches every joined machine with no further code, and its page lists them.
- What a device and a machine say to each other is sealed for the two of them. The hub passes it on and can't read it.
- The daemon still listens on nothing but its socket.
isc hubis one more client of it. See In a browser and Joining another machine to your hub.