<div class="gmail_quote">On Wed, Jan 4, 2012 at 3:30 PM, Brian Mattern <span dir="ltr"><<a href="mailto:rephorm@rephorm.com">rephorm@rephorm.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div><div></div><div class="h5">On Wed, 04 Jan 2012, Jorge Almeida wrote:<br>
<br>
> On Wed, Jan 4, 2012 at 3:11 PM, Mikael Magnusson <<a href="mailto:mikachu@gmail.com">mikachu@gmail.com</a>> wrote:<br>
> > On 4 January 2012 15:38, Jorge Almeida <<a href="mailto:jjalmeida@gmail.com">jjalmeida@gmail.com</a>> wrote:<br>
> >> On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson <<a href="mailto:mikachu@gmail.com">mikachu@gmail.com</a>> wrote:<br>
> >>> On 4 January 2012 12:54, Jorge Almeida <<a href="mailto:jjalmeida@gmail.com">jjalmeida@gmail.com</a>> wrote:<br>
> >>>> I've noticed a problem with rxvt-unicode: when a window is maximized, an<br>
> >>>> obnoxious unusable strip appears at the bottom of the window (about 1/2<br>
> >>>> cm of heigth). The strip disappears when the window is unmaximized. I<br>
> >>>> have no idea whether this happens in other WMs. I currently have no<br>
> >>>> other WM installed. xterm does not exhibit this behavior. Anyone with<br>
> >>>> this problem?<br>
> >>>><br>
> ><br>
> > Could you explain what the actual problem is? xterm behaves the same<br>
> > as urxvt for me, ie, any line or column that cannot fully fit a cell<br>
> > is left empty and unused.<br>
> ><br>
> <a href="http://www.math.ist.utl.pt/~jalmeida/urxvt_max.png" target="_blank">http://www.math.ist.utl.pt/~jalmeida/urxvt_max.png</a><br>
> <a href="http://www.math.ist.utl.pt/~jalmeida/xterm_max.png" target="_blank">http://www.math.ist.utl.pt/~jalmeida/xterm_max.png</a><br>
> <a href="http://www.math.ist.utl.pt/~jalmeida/nomax.png" target="_blank">http://www.math.ist.utl.pt/~jalmeida/nomax.png</a><br>
><br>
> The first picture shows the obnoxious dark blue strip at the bottom, the<br>
> second doesn't. Both have a regular blue strip that is vim-specific, and<br>
> has nothing to do with this. In bash, writing at the bottom of the<br>
> maximized urxvt window means writing just above the dark blue strip,<br>
> which is annoying. The third shows non-maximized windows, with the<br>
> expected behavior.<br>
><br>
> Of course, this problem may not be related to openbox at all...<br>
<br>
</div></div>It looks like when maximized, openbox forces the window to be the actual<br>
size of the 'maximized' region, instead of respecting its request to<br>
only be multiples of a given size. So, this leaves a space at the bottom<br>
of the window that rxvt cannot use.<br>
<br>
Maybe openbox should be changed to respect size increments when<br>
maximizing a window? (i.e., make it the largest multiple of the<br>
increment that is smaller than the available space)<br></blockquote><div><br></div><div>It used to, it changed for good reason.</div></div>