mirror of
https://github.com/l0ng-ai/tty7.git
synced 2026-10-03 16:01:59 +00:00
l0ng-ai
cf0e8f02e6
* feat(sidebar): keep pinned groups on the workspace and derive the rest Replace the sidebar's hand-made groups with the model from #955: the sidebar groups tabs by repo automatically, and you pin what you want to keep. - Pinned groups (`PinnedGroup`: id, optional name, optional folder, fold) are stored on the workspace in the machine tree, in display order, and a tab points at one by `GroupId`. Everything else is an auto group worked out every frame and never stored: by repo home, or by `user@host` for an SSH pane — native or a shell that ssh'd onward — so `/home/ubuntu` on two machines no longer lands under one header. - A tab whose cwd *enters* a pinned folder joins it (deepest folder wins; a repo home equal to the folder counts, which keeps worktrees with their repo). It is edge-triggered through `EntryWatch`, so a tab dragged out while still inside the folder stays out until it leaves and comes back, and a tab restored at launch is not pulled in by where it already sits. - Groups sync as one `WorkspaceSetGroups` / `GroupsChanged`, pushed only from an edit and adopted from every pull, so a fresh window can never push an empty set over the workspace's. The machine hands tabs naming a dropped group back to auto grouping in the same mutation. Control dialect → v11. - Config: `sidebar_grouping` (three modes) and `sidebar_collapsed_groups` give way to one `sidebar_auto_grouping` toggle; folds live with the workspace. - `tty7 tab ls` reports the pinned group a tab is in (name or folder leaf; JSON carries id, name and folder). * feat(sidebar): draw pinned groups above a divider, with their own gestures The sidebar now reads as two halves: the groups you keep, in the order you put them, then a divider, then the groups it works out (Arc-style). - Pinned headers drag-reorder among themselves (their own reorder surface, so a pinned header cannot be dropped among the derived ones); the order lands on the workspace's group list, not on the tabs. - An auto header carried above the divider is pinned when let go. With nothing pinned yet the divider appears during that drag as a "Drop here to pin" zone, since a hairline at the top of the list is nothing to aim at. - A tab kept in a pinned group and dropped anywhere below the divider goes back to auto grouping; the divider lights to say so. - An empty pinned group stays, with a "+ New Tab" row that opens a tab in its folder (or where ⌘T would, for a label group) and files it there. - Folder groups carry a pin mark that unpins on click and a tooltip with the folder; auto headers show pin and "+" on hover. - Header menus: pinned — Rename, Set Folder… (local workspaces), Use Current Tab's Folder, Clear Folder, New Tab, Unpin (folder groups), Delete. Auto — Pin Group, New Tab. Nothing renames an auto group; nothing pins implicitly. * feat(sidebar): open folders as pinned groups from Finder, the file tree and the palette Every way into a pinned group the design calls for: - Drop a folder from Finder or Explorer onto the sidebar to pin it (a local workspace only — a dropped path is this machine's, and a folder group keeps a directory on the workspace's host). Files are let fall. - "Pin as Group" on a folder in the file tree, on local and remote workspaces alike, since the tree and the group are both on the workspace's host. - Palette "New Group" makes an empty label group and opens its name for typing; "Open Folder as Group…" picks a folder with the system picker, pins it and opens a tab in it. The picker browses this computer, so that one is not offered on a remote workspace. - Tab right-click "Move to Group" lists the pinned groups plus "New Group…", which files the tab in a fresh label group with its name open for typing. Pinning a folder already pinned hands back the group that keeps it rather than making a second one to split its tabs with. * fix(sidebar): let groups that arrive from elsewhere pull no tab into a folder A window draws its first frames before its copy of the workspace's groups lands, so every tab's entry watch recorded "in no folder" — and the groups landing then read as each tab walking into its folder. A restored tab, or one dragged out of its folder group, was pulled back in on every launch. Groups adopted from a pull or from another window's `GroupsChanged` now start every tab's watch over from where it is; only this window's own pin gathers the tabs inside the folder, and says so tab by tab. A tab also goes up with the group it names even when the window does not know that group yet, so a sync in that same gap cannot send every kept tab back to auto grouping. * docs(sidebar): describe pinned and auto groups, and log the change Rewrite the sidebar page's grouping section around "grouped by repo automatically; pin what you want to keep": the divider, folder and label groups, the edge-triggered join, every way to pin, and the header menus. The configuration reference swaps `sidebar_grouping` for `sidebar_auto_grouping`, the CLI reference describes the GROUP column as the pinned group, and the changelog gains an Unreleased entry (#955). * fix(sidebar): file a tab opened by the CLI in a pinned folder into it A tab that reaches a window as TabCreated — from `tty7 tab new` or another window — started its entry watch as a restored tab, so opening one inside a pinned folder left it in the auto group below. It is as new as a tab opened here, and now joins the folder like one; every window that hears of it reaches the same answer. * test(machine): build the group sets in their initializers Clippy's field_reassign_with_default on the two WorkspaceGroups the set-groups test assembles. * fix(sidebar): draw restored tabs in their auto group, and title by repo again Auto groups are not stored, so after a restart every tab sat in Ungrouped until its own repo probe came back, then jumped; before pinned groups the stored repo key put it in place on the first frame. Each tab now carries `last_auto`, the auto group it last resolved to, as a hint: stored with the tab, sent up alongside its group in `TabSetGroup` whenever the live answer moves, and used to draw the tab until the probe answers. The probe always wins and rewrites the hint, and the hint never outranks a pinned group or the folder-entry rule. Another window's hint only fills a gap, so two windows can never bounce a disagreement between them. The workspace's fallback title regained the repo majority it lost: the most common pinned folder first, then the repo most unpinned tabs were last filed under (a worktree counting toward its repo home), then a pane's cwd. * refactor: drop what the new sidebar left unused, and two clippy findings - `TerminalView::native_ssh_cwd` and its helper existed for the sidebar's old folder grouping of native SSH panes; an SSH tab now groups by host, and nothing else read it. - The file tree's context menu takes `cx` instead of `danger` and the new groups flag, back to the argument count it had on main. - A title test builds its workspace in the initializer.
110 lines
4.2 KiB
Plaintext
110 lines
4.2 KiB
Plaintext
---
|
|
title: "Settings"
|
|
description: "What lives in each section, and how the settings file works."
|
|
---
|
|
|
|
<kbd>⌘ ,</kbd> opens Settings. There is a search box at the top that matches
|
|
setting names *and* keywords, which is usually faster than remembering which
|
|
section something is in.
|
|
|
|
<Frame caption="Settings opens in its own window, sections down the left">
|
|
<img src="/images/settings.webp" alt="tty7 Settings" />
|
|
</Frame>
|
|
|
|
## The eight sections
|
|
|
|
<CardGroup cols={2}>
|
|
<Card title="General" icon="sliders">
|
|
Interface language, startup and layout restore, tray icon, default terminal,
|
|
command completion notifications, update preferences and proxy, and the
|
|
tty7 server.
|
|
</Card>
|
|
<Card title="Appearance" icon="palette" href="/customization/themes">
|
|
Theme and colors, interface and terminal fonts, cursor, background image,
|
|
transparency, and inactive panes.
|
|
</Card>
|
|
<Card title="Terminal" icon="terminal">
|
|
Shell and starting directory, prompt editor, completion and command history,
|
|
scrollback, scrolling, bell, and opening links and files.
|
|
</Card>
|
|
<Card title="Keyboard & Mouse" icon="keyboard" href="/customization/keybindings">
|
|
Keyboard shortcuts, Option as Meta, mouse behavior, selection, and clipboard.
|
|
</Card>
|
|
<Card title="Window & Tabs" icon="window-maximize">
|
|
Tab position and placement, sidebar auto grouping, diff previews, and what
|
|
SSH tabs are called.
|
|
</Card>
|
|
<Card title="SSH" icon="server" href="/remote/ssh">
|
|
Hosts, connection defaults, security, authentication, proxies, and forwarding.
|
|
</Card>
|
|
<Card title="Integrations" icon="robot" href="/agents/status">
|
|
AI agent hooks per machine and the tty7 command on PATH.
|
|
</Card>
|
|
<Card title="About" icon="circle-info" href="/reference/updates">
|
|
App information, version, manual update checks, and available updates.
|
|
</Card>
|
|
</CardGroup>
|
|
|
|
## Search and edit
|
|
|
|
Search matches setting names, descriptions, English aliases, and configuration
|
|
keys such as `mouse_zoom_modifier`. Ordinary results are editable directly;
|
|
use the path above a result to open its category. SSH, theme editors, and
|
|
keyboard shortcuts have dedicated views.
|
|
|
|
Use **Modified only** to find settings that differ from their defaults. A
|
|
modified setting offers **Reset setting**; installation and maintenance actions
|
|
do not have a generic reset.
|
|
|
|
Ordinary controls save automatically. Text fields commit valid values on Enter
|
|
or when focus leaves the field. Custom theme edits are previewed until you save;
|
|
cancel restores the original theme. SSH profiles also use explicit saving.
|
|
Leaving an edited form offers save, discard, or continue editing.
|
|
|
|
## The settings file
|
|
|
|
Everything the Settings window writes goes to one file:
|
|
|
|
| | |
|
|
|---|---|
|
|
| macOS / Linux | `~/.config/tty7/config.json` |
|
|
| Windows | `%APPDATA%\tty7\config.json` |
|
|
|
|
The one exception is your saved SSH hosts, which live beside it in
|
|
`servers.json` — so `config.json` can be synced between machines without
|
|
carrying your servers. [servers.json →](/reference/configuration#ssh)
|
|
|
|
Set `TTY7_CONFIG_DIR` to point the whole directory — config, themes, state —
|
|
somewhere else.
|
|
|
|
You can edit the file by hand; a handful of options exist only there. See the
|
|
[configuration reference](/reference/configuration) for every key, its type, and
|
|
its default.
|
|
|
|
### How it handles mistakes
|
|
|
|
The file is written atomically, and read forgivingly:
|
|
|
|
- **A missing key** means the default — you only have to write what you change.
|
|
- **An out-of-range number** is clamped into its band, not rejected.
|
|
- **An unrecognised enum value** falls back to the default with a log line,
|
|
rather than failing the whole file.
|
|
- **An unparseable file** is not overwritten. tty7 starts on defaults, keeps a
|
|
copy at `config.json.corrupt`, and says so in the log.
|
|
|
|
<Note>
|
|
A UTF-8 BOM at the start of the file is tolerated, which matters if you edited
|
|
it in a Windows editor.
|
|
</Note>
|
|
|
|
## Language
|
|
|
|
**Settings → General → Language** switches the interface between English,
|
|
简体中文, and 日本語. The choice is explicit — the system language is never
|
|
inferred — and CLI output stays English regardless, so agent and script
|
|
integrations keep a stable surface.
|
|
|
|
```json
|
|
{ "gui_language": "zh-CN" }
|
|
```
|