> First step: see if it's a problem in your configuration. > > Launch vim with: > gvim -N -u NONE -i NONE > > Does the same behavior occur?
Yes. So this test result concldes that there's no configuration problem. right? I am now more convinced that this is caused by a Cygwin Xwin (ver. 1.8.2) configuration/behavior/bug. I frequently update cygwin packages so it's likely this was introduced in one of the latest builds. Supporting that is the fact that this problem only started happening recently. thx, Yosi -- You received this message from the "vim_use" 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
