New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
File->Open does not update window content correctly - Appeared first in v7-3-638 #91
Comments
Original comment by |
Original comment by |
Original comment by |
Original comment by Attachments: |
Original comment by |
Original comment by
|
Original comment by |
Original comment by |
Original comment by |
Original comment by |
is there any differeces between vim and gvim in ubuntu system,i have navel used gvim. |
I have the same issue as GoogleCodeExporter using VMware Workstation 12.5 and Ubuntu 16.04 patched to latest. Existed in Ubuntu 14 and Workstation 12 as well. Host is a HP Z620. This only occurs on this host all 3 of Ubuntu I am running. Haven't noticed the issue on CentOS. Using --sync option is a workaround. |
Roughly speaking, X clients cannot update their window content until a certain event from the X11 server arrives at their event queue and then drives the event loop to invoke the callback function for update. As for the GTK2 GUI, the callback function for update is quite passive. It is associated with update events at initialization and never dissociated from them until the process terminates. In addition, there’s no code at all in the implementation to block update events at runtime. Moreover, as indicated in the top post:
and in @chrisbra's gtk2_force_redraw.diff, the callback function works as expected once it gets an update event or another event which induces update. In short, just like any other X clients, the GUI is made not to exercise its veto over any update requests. Accordingly, it is highly likely that either of the windowing system under a certain environment or the GTK library (or some interaction between them) prevents update events from being delivered to the GUI for the case in question. If this is the case, there’s nothing left for the GUI to do with. |
i am closing this, as this is no gvim issue. |
Original issue reported on code.google.com by
yerv...@gmail.com
on 3 Nov 2012 at 1:33The text was updated successfully, but these errors were encountered: