Grunt, after a few trials I found it was definitively an awesome configuration problem in migrating from the old user's configuration to the new one. All is ok with the default new awesome configuration, sorry for the noise.
On Wed, Apr 05, 2017 at 09:17:28PM -0400, James McCoy wrote: > On Mon, Mar 06, 2017 at 09:57:29AM +0100, Francesco Paolo Lovergine wrote: > > Package: vim-gtk > > Is this reproducible with vim-gtk3? > > > In order to reproduce the bug: > > > > - use a tiled window manager (wm): i'm using awesome for that, not sure > > about > > others. > > I'm using i3. > > > - load vim-gtk in a wm tab in 'max' mode. > > Does this mean "fullscreen" (no decorations) or just that it takes up > the entire tab? I'm using i3's fullscreen mode to try reproducing the > behavior. > > Also, do you mean tag here or a tabbed layout in a tag? > > > - create a new vim tab with :tabnew. > > - switch to another wm tab and switch back to the gvim-gtk wm tab. > > > > You will se a grey window with a blinking cursor. > > Unfortunately, I don't. Everything looks fine. Does this happen when > using "gvim -u NORC" or does it need something in your configuration? > > Cheers, -- Francesco P. Lovergine
