Re: Better handling of window margins

[martin rudalics]

> I agree.  But if we only care about showing the same buffer case, then
> we do really need to consider only the width of the text area when we
> decide whether to split horizontally or vertically, right?  Moreover,
> even when another buffer is shown in one of the two windows, the
> window that continues to display the original buffer should still have
> reasonable width of its text area, right?  And the only way to
> guarantee the latter is to consider the width of only the text area,
> excluding the margins.

I miss you here.  This discussion started with the problem that while
modes are able to readjust their margins when a window is split,
‘split-window-sensibly’ won't split the window because it looks only at
the width of the text area.  C-x 3 would fail in the same manner because
it would compare ‘window-min-width’ (whose "value has to accommodate two
text columns as well as margins, fringes, a scroll bar and a right
divider, if present") with a text only area.

>>   > We are still talking about splitting windows here, right?
>>
>> And about resizing windows, right?
>
> I wasn't aware that resizing windows was part of the use cases
> considered by this discussion.  How is it relevant?  What decisions
> during resizing depend on the margins?

When I split a window I have to shrink the original one.  When I have
two side by side window and want to enlarge one of them I have to shrink
the other one.  So we have to solve the same problem in both cases.

martin