[thomasfedb]

Fixes a regression of #1297 on GTK.

Issue
Splits can be dragged or resized down to 0px, which just looks like a thick divider. The 10px minimum from #1323 was lost in the GTK rewrite.

Fix
Splits are now at least one cell plus padding in size, and the divider can't be dragged past that. This also clamps keyboard resizes.

Tested on Fedora 44. Dragging and resize_split stop at one column or line. I believe that macOS already has its own minimum and is unchanged.

First pass written with Claude Code (Claude Opus 5.5), reviewed and reprompted by me.

[dkinzler]

One little bug I found with this is when you resize a split (with keybinds) in one direction until you have reached the minimum size, you can still further decrease the split ratio stored in the split tree until it is 0 by pressing your bind. Nothing will change visually, but if you then resize again in the other direction you might have to press your keybind multiple times before something happens or the resize will be too small, depending on the resize amount specified in your keybind.

[thomasfedb]

One little bug I found with this is when you resize a split (with keybinds) in one direction until you have reached the minimum size, you can still further decrease the split ratio stored in the split tree until it is 0 by pressing your bind. Nothing will change visually, but if you then resize again in the other direction you might have to press your keybind multiple times before something happens or the resize will be too small, depending on the resize amount specified in your keybind.

@dkinzler should now be addressed.

[jcollie]

@thomasfedb can you rebase this onto current main?

[thomasfedb]

@thomasfedb can you rebase this onto current main?

@jcollie done!

[jcollie]

A couple of things that I noticed:

• A window resize will now permanently change the split ratio.
• A padding-only config reload doesn't update the minimum.

[thomasfedb]

A couple of things that I noticed:

* A window resize will now permanently change the split ratio.

* A padding-only config reload doesn't update the minimum.

@jcollie Yep, that seemed like the simplest way to avoid strange behaviour but was a tradeoff
How about the following behaviour instead:

• When a window resize pushes a split to its minimum, the stored ratio is left alone, so the original proportions come back when the window grows.
• When resize_split is used on a split that's being held at its minimum, the split's displayed ratio is stored first and then resized from there.

Can certainly fix the config aspect.

[jcollie]

How about the following behaviour instead:

* When a window resize pushes a split to its minimum, the stored ratio is left alone, so the original proportions come back when the window grows.

* When resize_split is used on a split that's being held at its minimum, the split's displayed ratio is stored first and then resized from there.

That seems right. I'd also hook up notify::min-position in the same way as max-position.

[jcollie]

Config change update looks good.

[thomasfedb]

@jcollie updated as requested. Renamed propMaxPosition to propPositionLimits hope that's okay

[jcollie]

Approved pending CI