Wintty 1.0.0-rc.7 release notes

Highlights

• All editions: every new pane now starts from an environment built the moment the pane opens, the one a fresh logon would hand your user: system and user variables as the registry has them now, with both PATH scopes merged. A PATH entry an installer writes, or a variable you change in the system settings, reaches the next pane you open without restarting the app. If you launch Wintty from another program on purpose, a Visual Studio developer prompt for example, so that panes inherit that program's environment, set reload-env = false in the configuration file to keep the old behaviour.
• All editions: panes open at their real size now. A new pane used to start its shell on a default grid and resize the moment the window's true size arrived, and a restored session used to bring its panes back on a default grid before fitting them, so every resume opened with a resize in front of you. New panes and restored panes both start at the size the window actually gives them.
• All editions: a tab title follows its own pane now. A shell that sets its own title moves the title of the tab it runs in and none of its siblings', so a title stops drifting onto tabs running something else.
• All editions: you can say what a new pane runs. -e takes a command line and runs it in the window it opens; the command configuration key sets what panes run while you have not chosen an explicit default profile; an explicit default-profile wins over the key. A pane whose program exits cleanly closes itself, and a window that opened only to run -e's command leaves no session behind to restore.

Fixes

• All editions: the prompt is still there after you split a pane or resume a session. The resize those actions perform could drop cmd's prompt mark, leaving an empty line where the prompt belongs until the next keypress; the mark survives the resize now.
• All editions: the app starts on machines with no usable graphics hardware. The surface degrades instead of taking the whole app down at startup.
• All editions: deleting your configuration file while the app is running no longer stops later changes from taking effect until you restart. A disappearance is confirmed over a short interval before the app believes it, so an editor's rename-and-replace save dance no longer reads as a deletion either.
• All editions: keys that close things are spent on the closing. A key that closes a pane, and the close key on an update notice, no longer echo a character into the pane behind them.
• All editions: a pane that still owes a frame draws it while it is visible too, instead of leaving part of the window stale until something else forces a redraw.
• All editions: a few error messages named the terminal engine instead of the app. They say Wintty now.
• Pro and Pro Legacy: a pane the session daemon brings back gets the same freshly built environment as any other pane, so the user-PATH repair from rc.6 covers daemon-restored panes too.

Known issues

Warning

• An update toast button clicked more than a minute after the app was closed still only opens the app instead of acting.
• Changing the update channel quickly back and forth in the popover can silently drop one of the choices; making the choice again lands it.
• The Enter or Escape that closes the command palette can still echo its character into a sibling pane rather than the focused one.
• If the update fails, install this version from the download page.
• The Start menu's All apps entry can show a small, upscaled icon; the Desktop and Start menu shortcuts carry the proper icon.
• Pro and Pro Legacy: bringing a left-behind session daemon up to date is offered when the app notices it. Sessions with nothing running in them are handled on their own.

Who gets this version

Found a problem?

Say which version you are on. Bugs and feature ideas: deblasis/wintty issues. Anything with logs or crash dumps: Discord or @polyMatto on X, or by email, which is easy enough to find, not a public issue.