hmmm...
The issue is not resolved after all. It still happens, but much more rarely. If
I manage to reliably reproduce it I will let you know. I will probably open a
ticket on awesome too.
thanks for the help anyway :)
all the best
Panos
--
--
You received this message from the "vim_dev" m
2017-03-20 1:18 GMT+09:00 :
> Thank you both for your answer
>
> @Kazunobu Kuriyama
>
> > Workspace? IIRC, Awesome WM calls it tag or something like that... Is
> it a new feature or concept of Awesome v4 and hence a thing I should read
> the manual?
>
> No you are right. Tags is the proper term.
Thank you both for your answer
@Kazunobu Kuriyama
> Workspace? IIRC, Awesome WM calls it tag or something like that... Is it a
> new feature or concept of Awesome v4 and hence a thing I should read the
> manual?
No you are right. Tags is the proper term.
> Actually, I cloned the WM source a
In addition to Michal's note,
2017-03-18 18:01 GMT+09:00 :
> Hi all,
>
> I am facing an issue with gvim.
>
> I use archlinux + awesome tiling WM. The bug is not 100% reproducible but
> it does happen most of the time (e.g. 90%). The steps to reproduce are:
>
> 1. Open gvim in full screen mode.
>
> I use archlinux + awesome tiling WM. The bug is not 100% reproducible but it
> does happen most of the time (e.g. 90%). The steps to reproduce are:
>
> 1. Open gvim in full screen mode.
> 2. Create two buffers
> 3. Move to a different workspace (e.g. on the browswer)
> 4. return to the gvim work
Hi all,
I am facing an issue with gvim.
I use archlinux + awesome tiling WM. The bug is not 100% reproducible but it
does happen most of the time (e.g. 90%). The steps to reproduce are:
1. Open gvim in full screen mode.
2. Create two buffers
3. Move to a different workspace (e.g. on the browswe
