That does not necessarily occur only with awesome. I have the same problem
in awesome and in xfwm. And yes it is fair to assume that it is a vim bug.
You cannot do match. That seems like some memory access violation. And you
notice it more in awesome because, perhaps, more resizing is happening
On 04/30/2016 06:16 PM, Uli Schlachter wrote:
> Hi,
>
> Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
> [...]
>> When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
>> stderr.txt` I got the following in stdout.txt:
>> RenderBadPicture (invalid Picture parameter)
>> Vim: Got X
Also not helpful: have you tried just using vim in xterm? That works
great for me, but you might be using plugins/features that terminal vim
doesn't support. But, if you are just using vanilla Gvim, then you might
consider giving terminal vim a try.
Abe
On Sat, Apr 30, 2016 at 11:16 AM, Uli
Hi,
Am 30.04.2016 um 16:28 schrieb Jeroen Budts:
[...]
> When starting gvim with `strace gvim -V9log.txt file.tex > stdout.txt 2>
> stderr.txt` I got the following in stdout.txt:
> RenderBadPicture (invalid Picture parameter)
> Vim: Got X error
> Vim: Finished.
>
> Any help on this is much
Hi all,
A few days ago I started using Awesome as my window manager (running
inside XFCE on xubuntu 15.10). The versions from the repository are
v3.5.6 (awesome) and 7.4.712 (gvim). I upgraded Awesome to 3.5.9 using a
ppa[1].
When Gvim gets resized, either because I resize the master-pane of
