mirror of
https://github.com/stablyai/orca.git
synced 2026-11-15 02:17:31 +00:00
* fix(terminal): let a paired host expand ~ in the paths its terminals print A paired-server pane expanded `~/…` on this client, using HOME from the pane's startup env or a home guessed from the cwd. When the host's home was not under /home/<user>, /Users/<user> or /root, the link never appeared; when the guess was wrong, it named another file. The host now receives the `~/…` text and answers with its own home's path, as it already does for its local workspaces. WSL workspaces keep client-side expansion. Refs #35968 * fix(terminal): keep a paired pane's launch HOME for its ~ links Refs #35968 * fix(terminal): keep SSH homes client-expanded and open folder roots from paired ~ links A server that proxies an SSH workspace refuses ~ paths, so paired panes over one keep the client's expansion. A host-resolved ~ root that names a folder workspace now activates through the workspace dispatcher. Refs #35968 * fix(terminal): send a paired host one separator after ~ Hosts join what follows `~/` onto their home, so `~//work/file` became the absolute `/work/file` once the client forwarded `~` paths as printed. The client now collapses separators right after `~` before asking. Refs #35968 * fix(terminal): link a paired ~ folder path only when it names a workspace A home-relative path ending in a separator, such as ~/proj/src/, skipped the folder-link filter so its host could expand it, but only a workspace root opens from a click, so subfolders became links that did nothing. The host's answer must now name a workspace root. Refs #35968 * refactor(terminal): resolve a linked file's editor target in its own module The editor workspace, host and relative path a linked file opens under now come from resolveLinkedFileEditorTarget, keeping terminal-file-open-routing within the 300-line limit. No behaviour change. Refs #35968