I have the same behaviour as well as gvim not using my gnome2 settings
(unlike mozilla, pan2, etc..). I suspect gvim not doing something right
instead of ion not supporting it nicely.
>
> Hi everybody,
>
> i have a small problem with gvim. After starting gvim in a full heigth
> frame ( on a 1280x1024 screen ) there is an unused grey area of about 3
> lines heigth on the bottom of the frame. Mod+L does not help, because
> gvim seems to ignore a resize to the same size. Any real resizing (
> resize frame, move to a different frame, fullscreen ) fixes this.
> I tried to write a lua function that increases and decreases the frame
> size in one function, but ion does not tell the client about the resize
> until after the function execution. Now i settled to using Mod+Enter
> twice. Does anybody have a better hack?
> ( If the frame does not cover the whole hight, gvim behaves normally. )
>
> One thing (i think its the only one for now) i miss in ion is something
> similar to sticky windows. It would be nice to attach a client to more
> than one frame. It is obvious that a client can not be shown in multiple
> frames at the same time, but it could be in one frame on each workspace.
> Having something like Mod+Shift+A as attach_duplicate would be nice.
>
> Regards
> Nils
>
> Ps: I use ion exclusively for a month now and i wont go back.
>
> Btw: I am using debian ion-devel/unstable (20030627), vim-gtk/stable
> (6.1.018). gvim from testing and unstable shows the same behaviour.
>
>
>
> --
> panic ("No CPUs found. System halted.\n");
> 2.4.3 linux/arch/parisc/kernel/setup.c
>
> Nils Decker <[EMAIL PROTECTED]>
>
