Open a Tab with Its Panes Already in Place

Nash 0.7.3 adds pre-split tabs: one command opens a new tab with two or three equal columns. It also adds automatic configuration sync after an update, so an existing installation can pick up new settings and commands without replacing its configuration files.

Start with the Layout You Need

A shell, a development server, and a test runner often belong together. Opening three separate tabs makes switching easy, but hides two of them. Manually splitting a new tab works too, but repeats the same setup every time.

Use these shortcuts instead:

• SUPER+Shift+Y opens a new tab with two equal columns.
• SUPER+Shift+U opens a new tab with three equal columns.

SUPER means Command on macOS, or the Windows/Super key on other systems. The commands are also available as New Tab with 2 Panes and New Tab with 3 Panes in the command palette and Shell menu.

The new tab opens to the right of the active tab. It uses the current working directory, and focus stays in the leftmost pane. Start your interactive command there, then move to the other columns for supporting processes. Nash refuses the request if the available width cannot accommodate that many columns.

These commands create a new tab; they do not divide the pane you are already using. The Tabs guide documents the underlying SpawnTabWithColumns action.

New Defaults Without Replacing Your Files

In 0.7.3, the first launch after a version change merges missing defaults into nash.toml, themes.toml, commands.toml, and tasks.toml. Explicit values, comments, formatting, and key order are preserved, and changed files receive a .bak backup. Commented-out entries are intended to stay excluded rather than being reinserted.

You can inspect or run that merge yourself:

Deleting an unwanted default is not a durable exclusion: a later sync sees it as missing. In this release's copied-file model, commenting it out tells the merge to leave it out.

Historical Configuration Model

This describes 0.7.3, not the current command/task configuration model. Nash 0.10.0 later introduced bundled defaults with override layering for commands and tasks. Also, 0.9.1 fixed a case where comments at the end of a file could move into the wrong TOML table during sync. See Configuration Sync for those migration details before applying old configuration advice to a newer build.