From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: "Timed out waiting for property-notify event" on RealVNC 4.X
Date: Fri, 28 Apr 2006 09:29:46 -0600 [thread overview]
Message-ID: <e2tcem$eem$1@sea.gmane.org> (raw)
In-Reply-To: <17489.6150.795732.876588@chls308.ch.intel.com>
Andrew M. Scott wrote:
> PROBLEM:
>
> Emacs "Timed out waiting for property-notify event" on RealVNC 4.X
> vncconfig when a large (> 2.5MB) portion of text is kill-ring-save(d).
>
> Unfortunately, the EDA tool ascii log files we deal with are regularly
> larger than 2.5MB.
>
> Our use model is to run VNC viewer on one OS (e.g. WindowsXP Pro) and
> run the EDA tools, Emacs, vncserver and vnconfig binaries on gnu/linux
> platforms.
>
> I had not problem editing the same testcase in one vim-6.3 editor
> session and copying the file contents and pasting into another vim-6.3
> invocation, in the same VNC session.
...
> WORKAROUNDS/REMEDIES:
>
> 1. Is there a way that GNU Emacs can be made more "tolerant" of the
> "Emacs being flooded with selection requests" issue mentioned in
> etc/PROBLEMS for klipper? (I'm assuming at this point that the
> this is the problem is the same for vncconfig).
>
> I'm a gdb, C, and X11 programming novice. I'll need explicit
> instructions if there is any debugging assistance I can provide to
> narrow the problem.
>
> 2. Killing vncconfig 4.X isn't really a solution to my general need
> for cut/paste support between apps within/between VNC sessions,
> clients and/or Microsoft Windows apps.
Copy-and-pasting the entire content of each file is not really a
solution for file sharing between your GNU/Linux and Windows platforms.
Why not run Samba on the GNU/Linux machine?
--
Kevin Rodgers
Sr. Software Engineer, IHS
next prev parent reply other threads:[~2006-04-28 15:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-27 19:14 "Timed out waiting for property-notify event" on RealVNC 4.X Andrew M. Scott
2006-04-28 15:29 ` Kevin Rodgers [this message]
2006-05-01 14:00 ` Andy Scott
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='e2tcem$eem$1@sea.gmane.org' \
--to=ihs_4664@yahoo.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.