Yakov Lerner wrote: > On 11/5/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote: > > > > Ujjal Bose wrote: > > > > > I was having problem with cut-paste selections from X <-----> Windows > > > for gvim (6.2) , and this is the reply I got from the RealVNC team . > > > So is there a way to solve this in gvim ? > > > > > > Thanks in advance ! > > > > > > -Ujjal > > > > > > ---------- Forwarded message ---------- > > > From: James Weatherall <[EMAIL PROTECTED]> > > > Date: Nov 3, 2006 9:59 PM > > > Subject: RE: Xvnc cut paste problem > > > To: Ujjal Bose <[EMAIL PROTECTED]>, [EMAIL PROTECTED] > > > > > > Hi Ujjal, > > > > > > It sounds like gvim doesn't set the timestamp on the X selection correctly > > > when it sets it, so vncconfig doesn't think it's changed. Selecting text > > > in > > > another X application, then selecting the desired text in gvim should > > > cause > > > vncconfig to see the selection ownership change and to then send the gvim > > > text to the viewer. > > > > > > Cheers, > > > > > > Wez @ RealVNC Ltd. > > > > This is a known problem that nobody has found a solution for yet. The > > "Time" type is some special kind of timestamp. I don't even know how to > > get the timestamp for "now". That's why CurrentTime is used. Getting > > the timestamp from an event (e.g. a mouse click) is not always possible > > (e.g., in an xterm we don't get it) and certainly difficult to pass all > > the way from the input to the selection. > > > > Problem with Xvnc is that they stick to the specification instead of > > to what applications do in practice. > > Bram, > > I know how to fill the correct non-0 time in own_selection() > for xterm clipbpard and for Xt gui (we need to generate dummy > self-NotifyEvent to get timestamp). I did not know how to do it for gtk, > but looks like Brett have the solution for gtk. > > What do you say about adding option xcliptime with values > 0=>use 0L timestamp, 1=>fill non-0 timestamp ? It might be even > possible to auto-guess whether server supports 0L timestamp in > OwnSelection (can be xcliptime==2).
I don't like using an option for something that is actually something system-dependent. It's like telling the user we are incapable to figure it out so he has to do all the work to figure out how it should work himself. As mentioned before, using CurrentTime for the timestamp, as we do now, should work anyway. -- If Microsoft would build a car... ... Occasionally your car would die on the freeway for no reason. You would have to pull over to the side of the road, close all of the car windows, shut it off, restart it, and reopen the windows before you could continue. For some reason you would simply accept this. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
