headers
Mikael Magnusson | 4 Jan 2012 12:58
Picon

Re: urxvt maximized

On 4 January 2012 12:54, Jorge Almeida <jjalmeida@...> wrote:
> I've noticed a problem with rxvt-unicode: when a window is maximized, an
> obnoxious unusable strip appears at the bottom of the window (about 1/2
> cm of heigth). The strip disappears when the window is unmaximized. I
> have no idea whether this happens in other WMs. I currently have no
> other WM installed. xterm does not exhibit this behavior. Anyone with
> this problem?
>
> TIA

The alternative is an obnoxious 1/2cm strip of the background showing,
and not fully maximizing the window. I don't know what's so obnoxious
about it. If you use the inheritPixmap option, then urxvt will only
show it correctly in that strip in the latest version.

--

-- 
Mikael Magnusson
_______________________________________________
openbox mailing list
openbox@...
http://icculus.org/mailman/listinfo/openbox
Permalink | Reply |
headers
Jorge Almeida | 4 Jan 2012 15:38
Picon

Re: urxvt maximized

On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson <mikachu@...> wrote:
> On 4 January 2012 12:54, Jorge Almeida <jjalmeida@...> wrote:
>> I've noticed a problem with rxvt-unicode: when a window is maximized, an
>> obnoxious unusable strip appears at the bottom of the window (about 1/2
>> cm of heigth). The strip disappears when the window is unmaximized. I
>> have no idea whether this happens in other WMs. I currently have no
>> other WM installed. xterm does not exhibit this behavior. Anyone with
>> this problem?
>>
>> TIA
>
> The alternative is an obnoxious 1/2cm strip of the background showing,
> and not fully maximizing the window. I don't know what's so obnoxious

xterm maximizes properly, and it uses the same font as urxvt.

> about it. If you use the inheritPixmap option, then urxvt will only
> show it correctly in that strip in the latest version.

With inheritPixmap=true, the problem disappears, but I get the desktop
background as window background, which I don't want...

Jorge Almeida
_______________________________________________
openbox mailing list
openbox@...
http://icculus.org/mailman/listinfo/openbox
Permalink | Reply |
headers
Mikael Magnusson | 4 Jan 2012 16:11
Picon

Re: urxvt maximized

On 4 January 2012 15:38, Jorge Almeida <jjalmeida@...> wrote:
> On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson <mikachu@...> wrote:
>> On 4 January 2012 12:54, Jorge Almeida <jjalmeida@...> wrote:
>>> I've noticed a problem with rxvt-unicode: when a window is maximized, an
>>> obnoxious unusable strip appears at the bottom of the window (about 1/2
>>> cm of heigth). The strip disappears when the window is unmaximized. I
>>> have no idea whether this happens in other WMs. I currently have no
>>> other WM installed. xterm does not exhibit this behavior. Anyone with
>>> this problem?
>>>
>>> TIA
>>
>> The alternative is an obnoxious 1/2cm strip of the background showing,
>> and not fully maximizing the window. I don't know what's so obnoxious
>
> xterm maximizes properly, and it uses the same font as urxvt.
>
>> about it. If you use the inheritPixmap option, then urxvt will only
>> show it correctly in that strip in the latest version.
>
> With inheritPixmap=true, the problem disappears, but I get the desktop
> background as window background, which I don't want...

Could you explain what the actual problem is? xterm behaves the same
as urxvt for me, ie, any line or column that cannot fully fit a cell
is left empty and unused.

--

-- 
Mikael Magnusson
_______________________________________________
(Continue reading)

Permalink | Reply |
headers
Jorge Almeida | 4 Jan 2012 17:50
Picon

Re: urxvt maximized

On Wed, Jan 4, 2012 at 3:11 PM, Mikael Magnusson <mikachu@...> wrote:
> On 4 January 2012 15:38, Jorge Almeida <jjalmeida@...> wrote:
>> On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson
<mikachu@...> wrote:
>>> On 4 January 2012 12:54, Jorge Almeida <jjalmeida@...> wrote:
>>>> I've noticed a problem with rxvt-unicode: when a window is maximized, an
>>>> obnoxious unusable strip appears at the bottom of the window (about 1/2
>>>> cm of heigth). The strip disappears when the window is unmaximized. I
>>>> have no idea whether this happens in other WMs. I currently have no
>>>> other WM installed. xterm does not exhibit this behavior. Anyone with
>>>> this problem?
>>>>
>
> Could you explain what the actual problem is? xterm behaves the same
> as urxvt for me, ie, any line or column that cannot fully fit a cell
> is left empty and unused.
>
http://www.math.ist.utl.pt/~jalmeida/urxvt_max.png
http://www.math.ist.utl.pt/~jalmeida/xterm_max.png
http://www.math.ist.utl.pt/~jalmeida/nomax.png

The first picture shows the obnoxious dark blue strip at the bottom, the
second doesn't. Both have a regular blue strip that is vim-specific, and
has nothing to do with this. In bash, writing at the bottom of the
maximized urxvt window means writing just above the dark blue strip,
which is annoying. The third shows non-maximized windows, with the
expected behavior.

Of course, this problem may not be related to openbox at all...
(Continue reading)

Permalink | Reply |
headers
richo | 4 Jan 2012 20:34
Favicon
Gravatar

Re: urxvt maximized

On 04/01/12 16:50 +0000, Jorge Almeida wrote:
>On Wed, Jan 4, 2012 at 3:11 PM, Mikael Magnusson <mikachu@...> wrote:
>> On 4 January 2012 15:38, Jorge Almeida <jjalmeida@...> wrote:
>>> On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson
<mikachu@...> wrote:
>>>> On 4 January 2012 12:54, Jorge Almeida <jjalmeida@...> wrote:
>>>>> I've noticed a problem with rxvt-unicode: when a window is maximized, an
>>>>> obnoxious unusable strip appears at the bottom of the window (about 1/2
>>>>> cm of heigth). The strip disappears when the window is unmaximized. I
>>>>> have no idea whether this happens in other WMs. I currently have no
>>>>> other WM installed. xterm does not exhibit this behavior. Anyone with
>>>>> this problem?
>>>>>
>>
>> Could you explain what the actual problem is? xterm behaves the same
>> as urxvt for me, ie, any line or column that cannot fully fit a cell
>> is left empty and unused.
>>
>http://www.math.ist.utl.pt/~jalmeida/urxvt_max.png
>http://www.math.ist.utl.pt/~jalmeida/xterm_max.png
>http://www.math.ist.utl.pt/~jalmeida/nomax.png
>
>The first picture shows the obnoxious dark blue strip at the bottom, the
>second doesn't. Both have a regular blue strip that is vim-specific, and
>has nothing to do with this. In bash, writing at the bottom of the
>maximized urxvt window means writing just above the dark blue strip,
>which is annoying. The third shows non-maximized windows, with the
>expected behavior.
>
>Of course, this problem may not be related to openbox at all...
(Continue reading)

Permalink | Reply |
headers
Jorge Almeida | 4 Jan 2012 21:03
Picon

Re: urxvt maximized

On Wed, Jan 4, 2012 at 7:34 PM, richo <richo@...> wrote:
>
> Can you post your whole .Xdefaults?
>
> My urxvt just uses the same background color for the padding at the bottom
> of
> the screen.
>
I tried writing till the bottom of a maximized xterm window, and indeed
there is a strip that doesn't get used, so you are right and
the strip is always there, but it may not be visible if the color is the
same as in the background. The resource is URxvt.borderColor. I didn't
have it in xterm, and so I missed the culprit.
Still, eliminating the border color makes an ugly non-maximized window.
It is a shame that the bottom border is so huge when the window is
maximized, but I suppose there's nothing to be done...

Thanks

Here is my (rather small) ~/.Xresources:

URxvt*font:             xft:Bitstream Vera Sans Mono:style=Regular:pixelsize=13
URxvt*background:       #FFFED2
URxvt*foreground:       #000000
URxvt*color14:       #9405AB
URxvt*geometry:      75x22
URxvt.scrollBar_right:	True
URxvt.scrollstyle:	rxvt
URxvt.scrollBar_align:	centre
URxvt.troughColor:       #D3D4FF
(Continue reading)

Permalink | Reply |
headers
Brian Mattern | 4 Jan 2012 21:30
Gravatar

Re: urxvt maximized

On Wed, 04 Jan 2012, Jorge Almeida wrote:

> On Wed, Jan 4, 2012 at 3:11 PM, Mikael Magnusson <mikachu@...> wrote:
> > On 4 January 2012 15:38, Jorge Almeida <jjalmeida@...> wrote:
> >> On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson
<mikachu@...> wrote:
> >>> On 4 January 2012 12:54, Jorge Almeida <jjalmeida@...> wrote:
> >>>> I've noticed a problem with rxvt-unicode: when a window is maximized, an
> >>>> obnoxious unusable strip appears at the bottom of the window (about 1/2
> >>>> cm of heigth). The strip disappears when the window is unmaximized. I
> >>>> have no idea whether this happens in other WMs. I currently have no
> >>>> other WM installed. xterm does not exhibit this behavior. Anyone with
> >>>> this problem?
> >>>>
> >
> > Could you explain what the actual problem is? xterm behaves the same
> > as urxvt for me, ie, any line or column that cannot fully fit a cell
> > is left empty and unused.
> >
> http://www.math.ist.utl.pt/~jalmeida/urxvt_max.png
> http://www.math.ist.utl.pt/~jalmeida/xterm_max.png
> http://www.math.ist.utl.pt/~jalmeida/nomax.png
> 
> The first picture shows the obnoxious dark blue strip at the bottom, the
> second doesn't. Both have a regular blue strip that is vim-specific, and
> has nothing to do with this. In bash, writing at the bottom of the
> maximized urxvt window means writing just above the dark blue strip,
> which is annoying. The third shows non-maximized windows, with the
> expected behavior.
>
(Continue reading)

Permalink | Reply |
headers
Dana Jansens | 4 Jan 2012 21:37

Re: urxvt maximized

On Wed, Jan 4, 2012 at 3:30 PM, Brian Mattern <rephorm <at> rephorm.com> wrote:
On Wed, 04 Jan 2012, Jorge Almeida wrote:

> On Wed, Jan 4, 2012 at 3:11 PM, Mikael Magnusson <mikachu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> > On 4 January 2012 15:38, Jorge Almeida <jjalmeida-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >> On Wed, Jan 4, 2012 at 11:58 AM, Mikael Magnusson <mikachu-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >>> On 4 January 2012 12:54, Jorge Almeida <jjalmeida-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >>>> I've noticed a problem with rxvt-unicode: when a window is maximized, an
> >>>> obnoxious unusable strip appears at the bottom of the window (about 1/2
> >>>> cm of heigth). The strip disappears when the window is unmaximized. I
> >>>> have no idea whether this happens in other WMs. I currently have no
> >>>> other WM installed. xterm does not exhibit this behavior. Anyone with
> >>>> this problem?
> >>>>
> >
> > Could you explain what the actual problem is? xterm behaves the same
> > as urxvt for me, ie, any line or column that cannot fully fit a cell
> > is left empty and unused.
> >
> http://www.math.ist.utl.pt/~jalmeida/urxvt_max.png
> http://www.math.ist.utl.pt/~jalmeida/xterm_max.png
> http://www.math.ist.utl.pt/~jalmeida/nomax.png
>
> The first picture shows the obnoxious dark blue strip at the bottom, the
> second doesn't. Both have a regular blue strip that is vim-specific, and
> has nothing to do with this. In bash, writing at the bottom of the
> maximized urxvt window means writing just above the dark blue strip,
> which is annoying. The third shows non-maximized windows, with the
> expected behavior.
>
> Of course, this problem may not be related to openbox at all...

It looks like when maximized, openbox forces the window to be the actual
size of the 'maximized' region, instead of respecting its request to
only be multiples of a given size. So, this leaves a space at the bottom
of the window that rxvt cannot use.

Maybe openbox should be changed to respect size increments when
maximizing a window? (i.e., make it the largest multiple of the
increment that is smaller than the available space)

It used to, it changed for good reason.
_______________________________________________
openbox mailing list
openbox@...
http://icculus.org/mailman/listinfo/openbox
Permalink | Reply |
headers
Mikael Magnusson | 4 Jan 2012 21:38
Picon

Re: urxvt maximized

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

Clearly showing whatever is behind the window is not going to be more
homogenous than what he has now :). I already mentioned this
possibility earlier in the thread. The icccm says the following:
"The base_width and base_height elements in conjunction with width_inc
and height_inc define an arithmetic progression of preferred window
widths and heights for nonnegative integers i and j".
Ie, preferred, not mandatory.

Also what dana said.

--

-- 
Mikael Magnusson
_______________________________________________
openbox mailing list
openbox@...
http://icculus.org/mailman/listinfo/openbox
Permalink | Reply |

Gmane