You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note that the sublayout `[2{13}1]` is treated as a single column when sizing is applied, so that set of panes as a whole receives `5` as its width relative to the other columns.
191
191
192
-
Top-level layout sizing (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.3) 🐣)
192
+
Top-level layout sizing (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.4) 🐣)
Since a sizing clause like `{123}` always _follows_ a pane count number within a layout, you may be wondering how sizing could be applied to the "top level" columns (or rows) of a layout. For example, given the layout `234`, how could you:
195
195
- make the first column `2` fill half the screen
196
196
- make the second column `3` fill a third of the screen
197
197
- make the third column `4` fill the remainder (one sixth) of the screen
198
198
199
-
This special case is handled by placing the sizing clause at the _start_ of the layout (prior to [v2](https://github.com/evnp/tmex/releases/tag/v2.0.3), this would result in an invalid layout error):
199
+
This special case is handled by placing the sizing clause at the _start_ of the layout (prior to [v2](https://github.com/evnp/tmex/releases/tag/v2.0.4), this would result in an invalid layout error):
200
200
```sh
201
201
tmex your-session-name --layout={321}234
202
202
>>>
@@ -221,7 +221,7 @@ tmex your-session-name --layout=[[234]{321}] # also equivalent
221
221
```
222
222
These may be functionally equivalent, but they're a far cry from intuitive! Feel free to use whichever of the three forms makes the most logical sense to you though.
223
223
224
-
Grid sub-layouts (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.3) 🐣)
224
+
Grid sub-layouts (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.4) 🐣)
Sometimes you might want a row/column of your layout to contain a grid of N panes, laid out using the default algorithm. This is done by placing `{+}`_after_ a number of panes in the layout. This can be thought of as "requesting a grid layout" for the preceeding number of panes – `+` is a visual mnemonic in that it separates the space within `{ }` in a grid-like formation.
because `5{+}` is expanded to `122`, which is the default grid layout when 5 panes are required. You can experiment with commands such as `tmex your-session-name --layout=7{+}` to see what default grid layout is produced for each number of panes. In general, each default grid layout attempts to equalize pane sizes, widths, and heights as much as possible, keeping the largest pane on the left with odd numbers of panes.
250
250
251
-
Multi-digit pane counts (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.3) 🐣)
251
+
Multi-digit pane counts (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.4) 🐣)
`11.` is treated as multi-digit, and produces a column 11 panes. `23` are treated as a sublayout of single-digit pane counts, producing 5 panes total. `45` have no adjacent `.` characters so they produce columns of 4 and 5 panes. `6.7` are treated as multi-digit, but still produce separate rows (in their sublayout) of 6 and 7 panes respectively – the `.` has no effect. Finally, `8.` is treated as multi-digit due to the adjacent `.` but still produces a column of 8 panes – the `.` has no effect).
274
274
275
-
Focused Pane Control (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.3) 🐣)
275
+
Focused Pane Control (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.4) 🐣)
You may want to create multiple tmux windows within your tmux session, and navigate between them using **CTRL+B→N** (next), **CTRL+B→P** (previous), **CTRL+B→[0-9]** (select by index).
**NOTE** that you must _always_ specify a top-level session name when using multiple windows, even if `--npm` / `-n` is specified. This is because npm-mode will be applied on a per-window basis, not to the session as a whole -- necessary if you want to run commands in _some_ windows as NPM scripts, but not commands in _all_ windows.
338
338
339
-
Usage within tmux sessions (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.3) 🐣)
339
+
Usage within tmux sessions (new in [v2](https://github.com/evnp/tmex/releases/tag/v2.0.4) 🐣)
You can use tmex within an existing tmux session to split panes or create additional windows, using the full suite of layout features. Usage within a tmux session will be automatically detected by tmex, and it will avoid spawning a nested tmux session. You may omit session name from the tmex command in these cases (otherwise it will be ignored):
342
342
```sh
@@ -352,7 +352,7 @@ tmex "cmd a" "cmd b" "cmd c" # INCORRECT - "cmd a" treated as session name and
0 commit comments