github unkn0wn-root/resterm v1.17.2

4 hours ago

v1.17.2

Clipboard over SSH (OSC 52)

  • No clipboard tool on the host (usual over SSH), so yank failed:
Clipboard unavailable; saved in editor register
  • Now the text goes to your terminal with OSC 52 and lands on your local clipboard:
Copied selection. Sent via OSC 52
  • Editor yank, delete, change and response pane copy.
  • Only when the clipboard tool fails. Working tool, no change.
  • Works by default in Kitty, Ghostty, WezTerm, Alacritty, foot, Windows Terminal.
  • iTerm2: Settings > General > Selection > "Applications in terminal may access clipboard".
  • Not supported: macOS Terminal, GNOME Terminal.
  • tmux: set -g set-clipboard on
  • Paste unchanged. p uses the editor register, terminal paste in insert mode uses your clipboard.

Troubleshooting

osc52_limit

  • Default 1 MiB, about 768 KB of text. Bigger copies stay in the editor register:
Too large for OSC 52 (limit 1 MiB). Saved in editor register
[clipboard]
osc52_limit = "8MiB"
  • JSON: {"clipboard":{"osc52_limit":"8MiB"}}
  • Raise it for Kitty. 16KiB for mosh.
  • KB, KiB, MB, MiB, GB, GiB, all powers of two. Must be greater than zero.

Configuration

Broken settings file no longer overwritten

  • A file that failed to load, for example diagnostics = 'yes', was replaced with defaults on the next theme change or layout save (g L).
  • With settings.json, a new settings.toml was written and the JSON file was ignored after that.
  • Now the save is refused and the status line shows why:
layout save error: settings not saved: parse settings "/home/you/.config/resterm/settings.toml": toml: cannot decode TOML string into struct field config.EditorSettings.Diagnostics of type *bool
  • Fix the file and restart.

Mock server, recorder and OAuth

  • :mock restart, :mock stop, the toggle key and quitting hung 3s:
Mock server stop failed: context deadline exceeded
  • Stopping the recorder: same 3s, Recorder stopped: context deadline exceeded.
  • OAuth auth code login: about 5s extra after "Authentication complete" in the browser.
  • Cause: a connection that never sent a request (Go 1.27 clients, browsers). Resterm waited about 5s for it.
  • Requests in progress still finish.

Don't miss a new resterm release

NewReleases is sending notifications on new releases.