Oh, one thing to ask you.

When scrolling forward, which side of the screen begins messing up on
drawing, upper side or lower side?

2016-02-04 1:00 GMT+09:00 Kazunobu Kuriyama <[email protected]>:

> 2016-02-03 23:59 GMT+09:00 Marius Gedminas <[email protected]>:
>
>> On Wed, Feb 03, 2016 at 11:10:22PM +0900, Kazunobu Kuriyama wrote:
>> > Marius,
>> >
>> > Just to make sure.
>> >
>> > Do you use the gvim on an X11 with a compositor or on a VM?
>>
>> I run gnome-shell, which is a compositor.  I run on native hardware
>> (Intel video on a ThinkPad X220).
>>
>
> Oh...  But I don't want to say, "Stop using it!" :)
>
>>
>> > Looking at the pictures you kindly uploaded, I can see what is cleared
>> by
>> > vim still remains on the screen.  It's just like as if clear
>> window/block
>> > clear operations were intentionally skipped
>>
>> But not all of them -- just some character cells!  And only when
>> scrolling forwards -- hitting PageUp redraws the screen correctly!
>>
>> It's as if clearing works, but outputting "text with spaces" skips
>> clearing the background behind each space character.
>>
>
> This additional info is quite helpful, from which we know where to start.
>
> While there're several issues we have to solve, let's focus on the "scroll
> forward" issue for now.  It's easier to attack than the visual quarks, that
> is, vague enemies like ghosts :)
>
>
>> > Actually, if I comment out drawing functions for clearing the window or
>> a
>> > block, I get a similar phenomenon in you reports.
>> >
>> > To deepen our understanding on the issue, I'd like to hear your
>> thoughts on
>> > possible causes of the failure of the clear operation.
>>
>> Could it be that vim computes the width of a space incorrectly (e.g. 0
>> pixels) because it has no visible pixels?  Or maybe the glyph is missing
>> in a font (because it's empty) and so it doesn't get drawn?
>>
>
> With your new info, I guess the bug lies in the functions for scrolling.
>
> Rather, I'd like to show my respects to someone who wrote vim's pango code.
>
>
>> Perhaps I'll find some time to debug this, as it seems like an
>> interesting problem -- I'm a bit daunted since I've no familiarity with
>> gvim's GUI drawing code, and also almost no familiarity with GTK+/Cairo
>> text drawing APIs.
>>
>
> Without your help, I couldn't know remaining issues other than my own.
> You're helping me much!
>
> Of course, I'd be happy if you would get familiar with that stuff :)
>
> Regards,
> Kazunobu
>
>>
>> Regards,
>> Marius Gedminas
>> --
>> Life begins when you can spend your spare time programming instead of
>> watching television.
>>                 -- Cal Keegan
>>
>> --
>> --
>> You received this message from the "vim_dev" maillist.
>> Do not top-post! Type your reply below the text you are replying to.
>> For more information, visit http://www.vim.org/maillist.php
>>
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "vim_dev" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
-- 
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

--- 
You received this message because you are subscribed to the Google Groups 
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Raspunde prin e-mail lui